From: Oleg Nesterov <oleg@redhat.com>
To: Michael Kerrisk <mtk.manpages@googlemail.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Bert Wesarg <bert.wesarg@googlemail.com>,
Ingo Molnar <mingo@elte.hu>, Roland McGrath <roland@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Strange stop-signal behavior in multithreaded program with defunct main
Date: Thu, 30 Oct 2008 19:10:51 +0100 [thread overview]
Message-ID: <20081030181051.GB11521@redhat.com> (raw)
In-Reply-To: <cfd18e0f0810300855w6e14bb81gfacd33d6bcb103b5@mail.gmail.com>
On 10/30, Michael Kerrisk wrote:
>
> On Thu, Oct 30, 2008 at 6:00 AM, Oleg Nesterov <oleg@redhat.com> wrote:
> > On 10/28, Michael Kerrisk wrote:
> >>
> >> Bert Wesarg described a scenario that I quickly replicated on
> >> 2.6.28-rc2 (and 2.6.25 -- it's not a regression in 2.6.28-rc)
> >> using the program below: if we have a multithreaded process
> >> with a defunct main thread running on a tty, and that
> >> process is sent a stop signal (either ^Z (SIGTSTP) or a stop
> >> signal sent from another terminal using kill(1)), then:
> >>
> >> a) the terminal is locked up; and
> >>
> >> b) the program is unresponsive to any other signal, except SIGKILL
> >> or SIGCONT.
> >
> > Yes, known problem. Please look at
> >
> > [RFC,PATCH 3/3] do_wait: fix waiting for stopped group with dead leader
> > http://marc.info/?t=119713920000003
>
> Okay -- thanks for the info. I've added some text to man-pages to
> cover this bug.
Well, we should fix this bug, of course.
I'll try to redo my old patch, but fyi I am very busy right now, and
most probably I will be completely offline during the next week.
Oleg.
prev parent reply other threads:[~2008-10-30 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 4:29 Strange stop-signal behavior in multithreaded program with defunct main Michael Kerrisk
2008-10-30 11:00 ` Oleg Nesterov
2008-10-30 15:55 ` Michael Kerrisk
2008-10-30 18:10 ` Oleg Nesterov [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=20081030181051.GB11521@redhat.com \
--to=oleg@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bert.wesarg@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtk.manpages@googlemail.com \
--cc=roland@redhat.com \
--cc=torvalds@linux-foundation.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