mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michael Kerrisk" <mtk.manpages@googlemail.com>
To: "Oleg Nesterov" <oleg@redhat.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 10:55:40 -0500	[thread overview]
Message-ID: <cfd18e0f0810300855w6e14bb81gfacd33d6bcb103b5@mail.gmail.com> (raw)
In-Reply-To: <20081030110000.GA3767@redhat.com>

Hi Oleg,

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.

Cheers,

Michael

--- a/man3/pthread_exit.3
+++ b/man3/pthread_exit.3
@@ -21,7 +21,7 @@
 .\" Formatted or processed versions of this manual, if unaccompanied by
 .\" the source, must acknowledge the copyright and authors of this work.
 .\"
-.TH PTHREAD_EXIT 3 2008-10-24 "Linux" "Linux Programmer's Manual"
+.TH PTHREAD_EXIT 3 2008-10-30 "Linux" "Linux Programmer's Manual"
 .SH NAME
 pthread_exit \- terminate calling thread
 .SH SYNOPSIS
@@ -87,6 +87,18 @@ The value pointed to by
 .IR retval
 should not be located on the calling thread's stack,
 since the contents of that stack are undefined after the thread terminates.
+.SH BUGS
+Currently,
+.\" Linux 2.6.27
+there are limitations in the kernel implementation logic for
+.BR wait (2)ing
+on a stopped thread group with a dead thread group leader.
+This can manifest in problems such as a locked terminal if a stop signal is
+sent to a foreground process whose thread group leader has already called
+.BR pthread_exit (3).
+.\" FIXME . review a later kernel to see if this gets fixed
+.\" http://thread.gmane.org/gmane.linux.kernel/611611
+.\" http://marc.info/?l=linux-kernel&m=122525468300823&w=2
 .SH SEE ALSO
 .BR pthread_create (3),
 .BR pthread_join (3),

  reply	other threads:[~2008-10-30 15:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-29  4:29 Michael Kerrisk
2008-10-30 11:00 ` Oleg Nesterov
2008-10-30 15:55   ` Michael Kerrisk [this message]
2008-10-30 18:10     ` Oleg Nesterov

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=cfd18e0f0810300855w6e14bb81gfacd33d6bcb103b5@mail.gmail.com \
    --to=mtk.manpages@googlemail.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@gmail.com \
    --cc=oleg@redhat.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

all inboxes | Powered by JetHome®