Re: [PATCH 0/6] Extended file stat system call
From: David Howells <hidden>
Date: 2012-04-27 09:19:09
Also in:
linux-cifs, linux-ext4, linux-fsdevel, linux-nfs
Possibly related (same subject, not in this thread)
- 2012-05-10 · Re: [PATCH 0/6] Extended file stat system call · David Howells <dhowells@redhat.com>
- 2012-04-28 · Re: [PATCH 0/6] Extended file stat system call · Dave Chinner <david@fromorbit.com>
- 2012-04-28 · Re: [PATCH 0/6] Extended file stat system call · Steve French <smfrench@gmail.com>
- 2012-04-28 · Re: [PATCH 0/6] Extended file stat system call · Dave Chinner <hidden>
- 2012-04-27 · Re: [PATCH 0/6] Extended file stat system call · Paul Eggert <hidden>
Andreas Dilger [off-list ref] wrote:
quoted
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 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html