From: Thayne Harbaugh <tharbaugh@lnxi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: klibc@zytor.com, linux-kernel@vger.kernel.org,
linux-hotplug-devel@lists.sourceforge.net
Subject: Re: chicken/egg between pipefs and initramfs/hotplug
Date: Thu, 28 Oct 2004 14:23:46 +0000 [thread overview]
Message-ID: <1098973426.1432.41.camel@tubarao> (raw)
In-Reply-To: <20041026162922.0e9f7f88.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]
Sorry to take so long to reply.
On Tue, 2004-10-26 at 16:29 -0700, Andrew Morton wrote:
> Thayne Harbaugh <tharbaugh@lnxi.com> wrote:
> >
> > It appears that linux/init/main.c:init() has a chicken/egg problem.
> > Apparently modprobe and other programs need a pipe and pipefs isn't
> > mounted until later on in do_basic_setup()/do_initcalls(). That means
> > that linux/fs/pipe.c:static struct vfsmount *pipe_mnt; isn't
> > initialized and blows up when it's derefernced in
> > linux/fs/pipe.c:get_pipe_inode().
>
> That's a bit sad. Does this fix it?
>
> --- 25/fs/pipe.c~a Tue Oct 26 16:28:44 2004
> +++ 25-akpm/fs/pipe.c Tue Oct 26 16:28:52 2004
> @@ -718,5 +718,5 @@ static void __exit exit_pipe_fs(void)
> mntput(pipe_mnt);
> }
>
> -module_init(init_pipe_fs)
> +fs_initcall(init_pipe_fs)
> module_exit(exit_pipe_fs)
> _
Works great, other than the omitted ';' for the fs_initcall():
--- fs/pipe.c.orig 2004-10-28 08:59:47.383192448 -0600
+++ fs/pipe.c 2004-10-28 08:57:07.746460920 -0600
@@ -718,5 +718,5 @@
mntput(pipe_mnt);
}
-module_init(init_pipe_fs)
+fs_initcall(init_pipe_fs);
module_exit(exit_pipe_fs)
Thanks.
--
Thayne Harbaugh
Linux Networx
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-28 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-25 18:30 chicken/egg between pipefs and initramfs/hotplug Thayne Harbaugh
2004-10-26 23:29 ` Andrew Morton
2004-10-28 14:23 ` Thayne Harbaugh [this message]
2004-10-28 7:23 ` Bob Barry
2004-10-28 7:42 ` Andrew Morton
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=1098973426.1432.41.camel@tubarao \
--to=tharbaugh@lnxi.com \
--cc=akpm@osdl.org \
--cc=klibc@zytor.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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