[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-kernel
Subject:    Re: Strange stop-signal behavior in multithreaded program with
From:       Oleg Nesterov <oleg () redhat ! com>
Date:       2008-10-30 10:00:12
Message-ID: 20081030110000.GA3767 () redhat ! com
[Download RAW message or body]

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

Oleg.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
[prev in list] [next in list] [prev in thread] [next in thread]