From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Mika Penttilä" <mika.penttila@kolumbus.fi>
Cc: Rene Mayrhofer <rene.mayrhofer@gibraltar.at>,
Jason Baron <jbaron@redhat.com>,
vda@port.imtp.ilyichevsk.odessa.ua,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: pivot_root seems to be broken in 2.4.21-ac4
Date: 23 Jul 2003 00:38:09 +0100 [thread overview]
Message-ID: <1058917089.4768.6.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <3F1DB75E.1050906@kolumbus.fi>
On Maw, 2003-07-22 at 23:14, Mika Penttilä wrote:
> /sbin/init used to start up with files->count > 1 and does
> close(0);close(1);close(2); -> kernel thread fds close.
>
> Now with unshare_files() and init's files->count ==1 the kernel threads
> /dev/console fds remain open. But one could ask of course so what :)
In other words the kernel side got caught out because it assumed
the bogus thread behaviour and needs some close() calls adding. That
would make sense.
next prev parent reply other threads:[~2003-07-22 23:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 20:53 pivot_root seems to be broken in 2.4.21-ac4 Rene Mayrhofer
2003-07-22 6:24 ` Denis Vlasenko
2003-07-22 6:50 ` Rene Mayrhofer
2003-07-22 17:37 ` Jason Baron
2003-07-22 17:40 ` Alan Cox
2003-07-22 18:03 ` Rene Mayrhofer
2003-07-22 20:00 ` Alan Cox
2003-07-22 20:37 ` Rene Mayrhofer
2003-07-22 21:54 ` Alan Cox
2003-07-23 6:23 ` pivot_root seems to be broken in 2.4.21-ac4 and 2.4.22-pre7 Rene Mayrhofer
2003-07-22 22:14 ` pivot_root seems to be broken in 2.4.21-ac4 Mika Penttilä
2003-07-22 23:38 ` Alan Cox [this message]
2003-07-23 6:30 ` pivot_root seems to be broken in 2.4.21-ac4 and 2.4.22-pre7 Rene Mayrhofer
2003-07-24 2:24 ` Jason Baron
2003-07-24 7:11 ` Rene Mayrhofer
2003-07-22 18:25 ` pivot_root seems to be broken in 2.4.21-ac4 Mika Penttilä
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=1058917089.4768.6.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.penttila@kolumbus.fi \
--cc=rene.mayrhofer@gibraltar.at \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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;
as well as URLs for NNTP newsgroup(s).