Re: [PATCH 0/6] Extended file stat system call
"Myklebust, Trond" <[email protected]>
| Newsgroups | gmane.linux.kernel.cifs,gmane.linux.file-systems,gmane.linux.nfs,gmane.network.samba.internals,gmane.comp.file-systems.ext4,gmane.comp.emulators.wine.devel,gmane.comp.kde.devel.kfm,gmane.comp.gnome.nautilus,gmane.linux.kernel.api |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 2012-04-26 at 22:57 +0100, David Howells wrote: > Myklebust, Trond <[email protected]> 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. > th > 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? Does it really matter whether it is the kernel or userland that is responsible for faking up inode numbers? If userland wants to use xstat() in order to fake up a stat() call, then it gets to take responsibility for the results. -- Trond Myklebust Linux NFS client maintainer NetApp [email protected] www.netapp.com