Re: knfsd and FS_REQUIRES_DEV

[Trond Myklebust <trond.myklebust@fys.uio.no>]

>>>>> " " == Linus Torvalds <torvalds@transmeta.com> writes:

     > Well, that actually could work with things like /proc, which
     > actually has meaningful inode numbers. They may not be stable
     > across reboots, of course, nor even really stable in general,
     > but in _theory_ there's nothing to keep us from exporting /proc
     > files and potentially other virtual filesystems.

I'd be really interested in seeing an NFS client caching protocol that
could cope with this...

For /proc you don't even *want* stability across reboots. That said,
even if you did, the current VFS API is quite sufficient to allow you
to create a protocol that will satisfy those stability
requirements.

The important thing as far as NFS filehandles are concerned is that
the actual information you put in is invariant over reboots, and that
it suffices to locate a file uniquely. With the current API, that
means that we need at least one unique number to identify the actual
'super_operations->fh_to_dentry()' method to be used. Beyond
that, it is entirely up to the fs how it wants to interpret the rest
of the filehandle...

Cheers,
   Trond