Re: [PATCH 0/6] Extended file stat system call
- From: David Howells <dhowells redhat com>
- To: Andreas Dilger <adilger dilger ca>
- Cc: "linux-cifs vger kernel org" <linux-cifs vger kernel org>, "linux-nfs vger kernel org" <linux-nfs vger kernel org>, "nautilus-list gnome org" <nautilus-list gnome org>, "libc-alpha sourceware org" <libc-alpha sourceware org>, "kfm-devel kde org" <kfm-devel kde org>, "wine-devel winehq org" <wine-devel winehq org>, "samba-technical lists samba org" <samba-technical lists samba org>, dhowells redhat com, Steve French <smfrench gmail com>, "linux-api vger kernel org" <linux-api vger kernel org>, "linux-fsdevel vger kernel org" <linux-fsdevel vger kernel org>, "linux-ext4 vger kernel org" <linux-ext4 vger kernel org>
- Subject: Re: [PATCH 0/6] Extended file stat system call
- Date: Fri, 27 Apr 2012 10:19:09 +0100
Andreas Dilger <adilger dilger ca> wrote:
> > However, since there is a remote file ID, we could add an
> > XSTAT_INFO_FILE_ID flag to indicate there's a standard xattr holding this.
>
> It is a bit strange that the kernel would return a flag that was not
> requested, but not fatal.
On the other hand, if it costs the kernel nothing to generate this indicator...
For network filesystems, for instance, you might know that there is some other
file ID because of the way the fs is specified.
I was thinking that many of the fields will be given values, even if you don't
ask for them, because the values (or approximations thereof) are present in
memory already.
David
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]