[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3279.1335518349@redhat.com>
Date: Fri, 27 Apr 2012 10:19:09 +0100
From: David Howells <dhowells@...hat.com>
To: Andreas Dilger <adilger@...ger.ca>
Cc: dhowells@...hat.com, Steve French <smfrench@...il.com>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-nfs@...r.kernel.org" <linux-nfs@...r.kernel.org>,
"linux-cifs@...r.kernel.org" <linux-cifs@...r.kernel.org>,
"samba-technical@...ts.samba.org" <samba-technical@...ts.samba.org>,
"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
"wine-devel@...ehq.org" <wine-devel@...ehq.org>,
"kfm-devel@....org" <kfm-devel@....org>,
"nautilus-list@...me.org" <nautilus-list@...me.org>,
"linux-api@...r.kernel.org" <linux-api@...r.kernel.org>,
"libc-alpha@...rceware.org" <libc-alpha@...rceware.org>
Subject: Re: [PATCH 0/6] Extended file stat system call
Andreas Dilger <adilger@...ger.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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists