On Tue, 11 Dec 2001, David S. Miller wrote:
> From: Elliot Lee <firstname.lastname@example.org>
> Date: Tue, 11 Dec 2001 19:13:48 -0500 (EST)
> I'm looking for information on knfsd's requirement that a filesystem be
> FS_REQUIRES_DEV in order to export it. Would someone point me in the right
> Needing to implement some not-quite-kosher exports,
> NFSD puts dev/ino into the filehandles it gives to the
> client, it uses this to lookup the inode in question.
I believe you're bringing up a requirement that inode numbers not change
while the filesystem is being exported, in order to avoid constant "stale
file handle" type of things. I can provide that guarantee (userland
filesystem via coda), but knfsd won't let me get that far because of its
more conservative policies right now.
I'm not worried about problems where files mysteriously disappear due to
me screwing up inode numbers in my code, only about causing kernel panics
or other Bad Things in the server's kernel. If I were to remove the
FS_REQUIRES_DEV check (or, more likely, submit a patch adding an nfsd
module option to remove the check...), what are the worst things that
could theoretically and realistically happen?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:22 EST