From: "David S. Miller" <davem@redhat.com>
To: paulus@samba.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: hang from HUP'ing init in linuxrc
Date: Mon, 2 Jul 2001 01:48:16 -0700 (PDT) [thread overview]
Message-ID: <15168.13648.602917.563647@pizda.ninka.net> (raw)
In-Reply-To: <15167.61332.139916.158874@cargo.ozlabs.ibm.com>
In-Reply-To: <15167.61332.139916.158874@cargo.ozlabs.ibm.com>
Paul Mackerras writes:
> What was happening was rather interesting. The init process was stuck
> inside prepare_namespace(), in the while loop here (this is lines 749
> - 751 of init/main.c):
>
> pid = kernel_thread(do_linuxrc, "/linuxrc", SIGCHLD);
> if (pid>0)
> while (pid != wait(&i));
>
...
[ no signal delivery due to returning to kernel space, blah blah blah
:-) ]
For 2.4.x I'd just check for sigpending in this wait loop.
Longer term (ie. 2.5.x and onward) we should look into ideas like those
mentioned by Ben. I for one would not complain about seeing dhcp
getting removed from the kernel :-)
Later,
David S. Miller
davem@redhat.com
prev parent reply other threads:[~2001-07-02 8:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-02 3:50 Paul Mackerras
2001-07-02 4:24 ` Ben LaHaise
2001-07-02 8:48 ` David S. Miller [this message]
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=15168.13648.602917.563647@pizda.ninka.net \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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
all inboxes | Powered by JetHome®