From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
Organization: CC CTU Prague
To: Neil Brown <neilb@cse.unsw.edu.au>
Date: Fri, 5 Mar 2004 11:47:08 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: [TRIVIAL][PATCH]:/proc/fs/nfsd/
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, okir@monad.swb.de,
       obelix123@toughguy.net
Message-ID: <16B99F21693@vcnet.vc.cvut.cz>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1066
Lines: 25

On  5 Mar 04 at 21:08, Neil Brown wrote:
> > The following patch fixes it.
> 
> Does it need fixing??
> 
> If you remove this, then people who compile a kernel without nfsd
> support, and then later decide to compile an nfsd module and load it,
> will not be able to mount the nfsd filesystem at the right place.

> I think it is a very small cost, and a measurable gain, to leave it
> there.

Maybe I'm stupid, but why cannot knfsd module create fs/nfsd
directory at module load? That way you can do insmod/modprobe followed 
by mount() to do that. And if you'll fiddle with do_mount a bit
(so that get_fs_type() is invoked before walking mount path)
you can do it even without modprobing knfsd in advance, by just
doing 'mount none /proc/fs/nfsd -t nfsd'.
                                                Petr Vandrovec

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/