This is the mail archive of the
mailing list for the glibc project.
Re: Extended file stat: Splitting file- and fs-specific info?
- From: David Howells <dhowells at redhat dot com>
- To: Dave Chinner <david at fromorbit dot com>
- Cc: dhowells at redhat dot com, adilger at dilger dot ca, bfields at fieldses dot org, smfrench at gmail dot com, ben at decadent dot org dot uk, Trond dot Myklebust at netapp dot com, roland at hack dot frob dot com, jra at samba dot org, bernd dot schubert at itwm dot fraunhofer dot de, linux-fsdevel at vger dot kernel dot org, linux-nfs at vger dot kernel dot org, linux-cifs at vger dot kernel dot org, samba-technical at lists dot samba dot org, linux-ext4 at vger dot kernel dot org, linux-api at vger dot kernel dot org, libc-alpha at sourceware dot org
- Date: Wed, 09 May 2012 10:21:14 +0100
- Subject: Re: Extended file stat: Splitting file- and fs-specific info?
- References: <20120509002420.GL5091@dastard> <firstname.lastname@example.org> <email@example.com>
Dave Chinner <firstname.lastname@example.org> wrote:
> I don't think we want to expose the inode generation numbers. It is
> trivial to construct NFS file handles (usually just fsid, inode
> number and generation) with that information and hence bypass
> security checks to access files.
I was asked for it by Bernd Schubert for userspace NFS servers and FUSE -
maybe he can say what he wants it for.
I also have a note that Jeremy Allison asked for it, but I can't find where or
why, so that might be an error.
It looks like FreeBSD do have an st_gen field in their stat struct, but it's
only filled in for root. Maybe I could do something like that?