From: Jason Lunz <lunz@gtf.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: jbaron@redhat.com, marcelo@conectiva.com.br,
linux-kernel@vger.kernel.org
Subject: Re: pivot_root solved by patch to 2.4.22-pre7
Date: Fri, 15 Aug 2003 14:14:19 -0400 [thread overview]
Message-ID: <20030815181418.GA9978@reflexsecurity.com> (raw)
In-Reply-To: <1060271448.3123.75.camel@dhcp22.swansea.linux.org.uk>
In gmane.linux.kernel, you wrote:
>> the unshare_files change causes init to no longer share the same fd table
>> with the other kernel threads. thus, when init closes or opens fds it does
>
> Ah yes.. because of do_basic_setup. Having /sbin/init sharing with
> kernel threads doesn't actually strike me as too clever anyway although
> none of them should be using fd stuff.
>
> In which case I guess we should call unshare_files directly before we
> open /dev/console in init/main.c.
Is this going to be fixed for 2.4.22? In -rc2, I still get this after
pivot_root (I'm using pivot_root, but not initrd):
halfoat:0:~ # umount /mnt
umount: /mnt: device is busy
halfoat:1:~ # lsof /mnt
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
keventd 2 root 0u CHR 5,1 21 /mnt/dev/console
keventd 2 root 1u CHR 5,1 21 /mnt/dev/console
keventd 2 root 2u CHR 5,1 21 /mnt/dev/console
ksoftirqd 3 root 0u CHR 5,1 21 /mnt/dev/console
ksoftirqd 3 root 1u CHR 5,1 21 /mnt/dev/console
ksoftirqd 3 root 2u CHR 5,1 21 /mnt/dev/console
ksoftirqd 4 root 0u CHR 5,1 21 /mnt/dev/console
ksoftirqd 4 root 1u CHR 5,1 21 /mnt/dev/console
ksoftirqd 4 root 2u CHR 5,1 21 /mnt/dev/console
kswapd 5 root 0u CHR 5,1 21 /mnt/dev/console
kswapd 5 root 1u CHR 5,1 21 /mnt/dev/console
kswapd 5 root 2u CHR 5,1 21 /mnt/dev/console
bdflush 6 root 0u CHR 5,1 21 /mnt/dev/console
bdflush 6 root 1u CHR 5,1 21 /mnt/dev/console
bdflush 6 root 2u CHR 5,1 21 /mnt/dev/console
kupdated 7 root 0u CHR 5,1 21 /mnt/dev/console
kupdated 7 root 1u CHR 5,1 21 /mnt/dev/console
kupdated 7 root 2u CHR 5,1 21 /mnt/dev/console
kjournald 64 root 0u CHR 5,1 21 /mnt/dev/console
kjournald 64 root 1u CHR 5,1 21 /mnt/dev/console
kjournald 64 root 2u CHR 5,1 21 /mnt/dev/console
Jason
next prev parent reply other threads:[~2003-08-15 18:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0308051506570.26542-100000@dhcp64-178.boston.redhat.com>
2003-08-06 6:27 ` pivot_root solved by patch to 2.4.22-pre7 Rene Mayrhofer
2003-08-06 19:33 ` Marcelo Tosatti
2003-08-06 19:51 ` Herbert Pötzl
2003-08-07 9:34 ` Andreas Haumer
2003-08-07 10:33 ` Rene Mayrhofer
2003-08-07 11:58 ` Alan Cox
2003-08-07 15:26 ` Jason Baron
2003-08-07 15:50 ` Alan Cox
2003-08-07 16:41 ` Jason Baron
2003-08-15 18:14 ` Jason Lunz [this message]
2003-09-23 17:25 Mathias Sundman
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=20030815181418.GA9978@reflexsecurity.com \
--to=lunz@gtf.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.