From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
To: linux-kernel@vger.kernel.org
Cc: user-mode-linux-devel@lists.sourceforge.net,
BlaisorBlade <blaisorblade_spam@yahoo.it>
Subject: Re: [uml-devel] 2.6.9-bb3 on 2.6.9 host problem - triggering a host bug?
Date: Wed, 01 Dec 2004 19:52:20 +0100 [thread overview]
Message-ID: <41AE12E4.9080609@fujitsu-siemens.com> (raw)
In-Reply-To: <200411301950.13529.blaisorblade_spam@yahoo.it>
Blaisorblade wrote:
> On Monday 29 November 2004 23:15, Blaisorblade wrote:
>
> However, I've now discovered that it only happens when CONFIG_STATIC_LINK is
> enabled - that makes the kernel die. The interesting thing is that it becomes
> unkillable
Have found the reason for the task to become unkillable, i.e. state 'D'.
There is a bug in 2.6.9 and up in fs/exec.c
If the kernel does coredump_wait(), it tries to kill all other threads, that are
running on the same mm. Therefore it calls "force_sig_specific(SIGKILL, p)".
But if one of the threads is on a ptrace-stop, SIGKILL has no effect.
The killing thread will wait forever in "D".
Bodo
parent reply other threads:[~2004-12-01 18:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200411301950.13529.blaisorblade_spam@yahoo.it>]
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=41AE12E4.9080609@fujitsu-siemens.com \
--to=bstroesser@fujitsu-siemens.com \
--cc=blaisorblade_spam@yahoo.it \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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®