From: Raj <obelix123@toughguy.net>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, okir@monad.swb.de
Subject: Re: [TRIVIAL][PATCH]:/proc/fs/nfsd/
Date: Fri, 05 Mar 2004 16:05:47 +0530 [thread overview]
Message-ID: <40485803.7060102@toughguy.net> (raw)
In-Reply-To: <16456.20875.670811.900445@notabene.cse.unsw.edu.au>
Neil Brown wrote:
>On Friday March 5, obelix123@toughguy.net wrote:
>
>
>>Hi,
>>
>>Kernel Version: 2.6.3
>>Even if NFSD is not selected, the proc entry /proc/fs/nfsd is getting
>>created.
>>
>>
>
>Is it a problem??
>
>
Theoritically no, but behavior wise , yes.
>
>
>>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 guess choosing nfsd either builtin or as a module will cause a rebuild
of some components of the main kernel and hence a
reboot is anyway need. Pls correct me if i am wrong.
>
>
>
>>Pls apply.
>>
>>/Raj
>>--- linux-2.6.3/fs/proc/root.c 2004-02-19 09:52:32.000000000 +0530
>>+++ linux-2.6.3-fixed/fs/proc/root.c 2004-03-05 13:48:28.448516568 +0530
>>@@ -65,7 +65,11 @@ void __init proc_root_init(void)
>> #endif
>> proc_root_fs = proc_mkdir("fs", 0);
>> proc_root_driver = proc_mkdir("driver", 0);
>>+
>>+#if defined(CONFIG_NFSD) || defined(CONFIG_NFSD_MODULE)
>> proc_mkdir("fs/nfsd", 0); /* somewhere for the nfsd filesystem to be mounted */
>>+#endif
>>+
>> #if defined(CONFIG_SUN_OPENPROMFS) || defined(CONFIG_SUN_OPENPROMFS_MODULE)
>> /* just give it a mountpoint */
>> proc_mkdir("openprom", 0);
>>
>>
>-
>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/
>
>
>
next prev parent reply other threads:[~2004-03-05 10:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 9:09 [TRIVIAL][PATCH]:/proc/fs/nfsd/ Raj
2004-03-05 10:08 ` [TRIVIAL][PATCH]:/proc/fs/nfsd/ Neil Brown
2004-03-05 10:35 ` Raj [this message]
2004-03-13 17:26 ` [TRIVIAL][PATCH]:/proc/fs/nfsd/ Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2004-03-05 9:47 [TRIVIAL][PATCH]:/proc/fs/nfsd/ Petr Vandrovec
2004-03-05 11:28 ` [TRIVIAL][PATCH]:/proc/fs/nfsd/ Neil Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40485803.7060102@toughguy.net \
--to=obelix123@toughguy.net \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=okir@monad.swb.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox