aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/tty/serial
diff options
context:
space:
mode:
authorOleg Nesterov <oleg@redhat.com>2011-09-26 19:06:32 +0200
committerGreg Kroah-Hartman <gregkh@suse.de>2011-11-11 09:36:23 -0800
commit43742b14ffbe87453e96f4411389445fc707df57 (patch)
tree42e98afb73a408e2cf9b3525648657f8c7612d2c /drivers/tty/serial
parenteb4b2df8f20d4479eceeb9bc51695caaa7bcd229 (diff)
downloadkernel_samsung_espresso10-43742b14ffbe87453e96f4411389445fc707df57.zip
kernel_samsung_espresso10-43742b14ffbe87453e96f4411389445fc707df57.tar.gz
kernel_samsung_espresso10-43742b14ffbe87453e96f4411389445fc707df57.tar.bz2
ptrace: don't clear GROUP_STOP_SIGMASK on double-stop
[This does not correspond to any specific patch in the upstream tree as it was fixed accidentally by rewriting the code in the 3.1 release] https://bugzilla.redhat.com/show_bug.cgi?id=740121 1. Luke Macken triggered WARN_ON(!(group_stop & GROUP_STOP_SIGMASK)) in do_signal_stop(). This is because do_signal_stop() clears GROUP_STOP_SIGMASK part unconditionally but doesn't update it if task_is_stopped(). 2. Looking at this problem I noticed that WARN_ON_ONCE(!ptrace) is not right, a stopped-but-resumed tracee can clone the untraced thread in the SIGNAL_STOP_STOPPED group, the new thread can start another group-stop. Remove this warning, we need more fixes to make it true. Reported-by: Luke Macken <lmacken@redhat.com> Signed-off-by: Oleg Nesterov <oleg@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/tty/serial')
0 files changed, 0 insertions, 0 deletions