SELinux: Don't flush inherited SIGKILL during execve()
authorDavid Howells <dhowells@redhat.com>
Wed, 29 Apr 2009 12:45:05 +0000 (13:45 +0100)
committerJames Morris <jmorris@namei.org>
Wed, 29 Apr 2009 23:07:13 +0000 (09:07 +1000)
commit3bcac0263f0b45e67a64034ebcb69eb9abb742f4
tree33f4db08edaa12e1c20df348e2fa28c7c2198ebe
parent88c48db9788862d0290831d081bc3c64e13b592f
SELinux: Don't flush inherited SIGKILL during execve()

Don't flush inherited SIGKILL during execve() in SELinux's post cred commit
hook.  This isn't really a security problem: if the SIGKILL came before the
credentials were changed, then we were right to receive it at the time, and
should honour it; if it came after the creds were changed, then we definitely
should honour it; and in any case, all that will happen is that the process
will be scrapped before it ever returns to userspace.

Signed-off-by: David Howells <dhowells@redhat.com>
Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Signed-off-by: James Morris <jmorris@namei.org>
include/linux/sched.h
kernel/signal.c
security/selinux/hooks.c