diff options
author | Oleg Nesterov <oleg@redhat.com> | 2009-04-02 16:58:02 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2009-04-02 19:04:58 -0700 |
commit | f008faff0e2777c8b3fe853891b774ca465938d8 (patch) | |
tree | d2f325995473a33652f7f7ead71e63d5298fbd01 /include/Kbuild | |
parent | 43918f2bf4806675943416d539d9d5e4d585ebff (diff) | |
download | kernel-crypto-f008faff0e2777c8b3fe853891b774ca465938d8.tar.gz kernel-crypto-f008faff0e2777c8b3fe853891b774ca465938d8.tar.xz kernel-crypto-f008faff0e2777c8b3fe853891b774ca465938d8.zip |
signals: protect init from unwanted signals more
(This is a modified version of the patch submitted by Oleg Nesterov
http://lkml.org/lkml/2008/11/18/249 and tries to address comments that
came up in that discussion)
init ignores the SIG_DFL signals but we queue them anyway, including
SIGKILL. This is mostly OK, the signal will be dropped silently when
dequeued, but the pending SIGKILL has 2 bad implications:
- it implies fatal_signal_pending(), so we confuse things
like wait_for_completion_killable/lock_page_killable.
- for the sub-namespace inits, the pending SIGKILL can
mask (legacy_queue) the subsequent SIGKILL from the
parent namespace which must kill cinit reliably.
(preparation, cinits don't have SIGNAL_UNKILLABLE yet)
The patch can't help when init is ptraced, but ptracing of init is not
"safe" anyway.
Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Acked-by: Roland McGrath <roland@redhat.com>
Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Daniel Lezcano <daniel.lezcano@free.fr>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include/Kbuild')
0 files changed, 0 insertions, 0 deletions