Fix signalfd interaction with thread-private signals
authorBenjamin Herrenschmidt <benh@kernel.crashing.org>
Mon, 11 Jun 2007 22:16:18 +0000 (08:16 +1000)
committerLinus Torvalds <torvalds@woody.linux-foundation.org>
Mon, 18 Jun 2007 17:18:32 +0000 (10:18 -0700)
commitcaec4e8dc85e0644ec24aeb36285e1ba02da58cc
treec40510afdc1676f268d14ecb8bfe2ab887cf0b0f
parentbd197234b0a616c8f04f6b682326a5a24b33ca92
Fix signalfd interaction with thread-private signals

Don't let signalfd dequeue private signals off other threads (in the
case of things like SIGILL or SIGSEGV, trying to do so would result
in undefined behaviour on who actually gets the signal, since they
are force unblocked).

Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Acked-by: Davide Libenzi <davidel@xmailserver.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
kernel/signal.c