[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4FAA6230.7040700@itwm.fraunhofer.de>
Date: Wed, 09 May 2012 14:25:20 +0200
From: Bernd Schubert <bernd.schubert@...m.fraunhofer.de>
To: Christoph Hellwig <hch@...radead.org>
CC: David Howells <dhowells@...hat.com>,
Dave Chinner <david@...morbit.com>, adilger@...ger.ca,
bfields@...ldses.org, smfrench@...il.com, ben@...adent.org.uk,
Trond.Myklebust@...app.com, roland@...k.frob.com, jra@...ba.org,
linux-fsdevel@...r.kernel.org, linux-nfs@...r.kernel.org,
linux-cifs@...r.kernel.org, samba-technical@...ts.samba.org,
linux-ext4@...r.kernel.org, linux-api@...r.kernel.org,
libc-alpha@...rceware.org
Subject: Re: Extended file stat: Splitting file- and fs-specific info?
On 05/09/2012 02:05 PM, Christoph Hellwig wrote:
> On Wed, May 09, 2012 at 01:55:16PM +0200, Bernd Schubert wrote:
>> The basic idea of generation numbers is to check if an inode was
>> recycled, so only if the tuple of inode-number and generation-number
>> matches we still have the same file. Kernel nfs
>
> NFS does not and should not look at the inode generation. Except for a
> bit of legacy code for the old pre-Linux 2.4 filehandles it looks at the
> opaque file handle returned and only interpreted by the filesystem. Any
> userspace NFS server should do the same.
Ok, I didn't look how kernel NFS does it for quite some time already...
User space NFS only can do it beginning with 2.6.39 - given that user
space also needs to support older kernels and other OSs, which might not
have open_by_handle, userspace unfortunately cannot entirely rely on
that feature.
Cheers,
Bernd
--
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