Re: [PATCH 20/40] mn10300: Use set_current_blocked() and block_sigmask()

From
David Howells <dhowells@redhat.com>
Date
2012-02-14 18:13:22
Also in
lkml
Reply to
Oleg Nesterov, 2012-02-14
Oleg Nesterov [off-list ref] wrote:
No, only current can change ->blocked. This is even documented in
sigprocmask(). And more, the only correct way to change ->blocked
is set_current_blocked(). OK, with a couple of "I know what I am
doing" exceptions in kernel/signal.c.
I was looking at force_sig_info() and derivatives.  Is that what you refer to?

If so, is it worth providing a force_sig_info_current(),
force_sigsegv_current() and force_sig_current() to make things clearer to grep
for, I wonder?

David
Thread (61 messages) 61 messages, 9 authors, last reply 2012-04-06
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help