* Re: [uml-devel] 2.6.9-bb3 on 2.6.9 host problem - triggering a host bug?
[not found] ` <200411301950.13529.blaisorblade_spam@yahoo.it>
@ 2004-12-01 18:52 ` Bodo Stroesser
0 siblings, 0 replies; only message in thread
From: Bodo Stroesser @ 2004-12-01 18:52 UTC (permalink / raw)
To: linux-kernel; +Cc: user-mode-linux-devel, BlaisorBlade
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2004-12-01 18:53 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <200411292315.25368.blaisorblade_spam@yahoo.it>
[not found] ` <200411301950.13529.blaisorblade_spam@yahoo.it>
2004-12-01 18:52 ` [uml-devel] 2.6.9-bb3 on 2.6.9 host problem - triggering a host bug? Bodo Stroesser
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®