[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <10104.1335477476@redhat.com>
Date: Thu, 26 Apr 2012 22:57:56 +0100
From: David Howells <dhowells@...hat.com>
To: "Myklebust, Trond" <Trond.Myklebust@...app.com>
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
Myklebust, Trond <Trond.Myklebust@...app.com> wrote:
> You are still not explaining why they need to know the values at all? If
> the values are bogus, then don't return them, and don't set the flag
> that says they are being returned.
What if the xstat() and struct xstat eventually becomes what userspace uses as
stat() (as a wrapper) and struct stat (if such a thing is possible with glibc
versioning)? Do older programs that think they're using stat() and don't know
about the extra fields available expect to see a useful value in st_ino?
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