signals: set_current_blocked() can use __set_current_blocked()
authorOleg Nesterov <oleg@redhat.com>
Sat, 5 Jan 2013 18:13:29 +0000 (19:13 +0100)
committerLinus Torvalds <torvalds@linux-foundation.org>
Sun, 6 Jan 2013 03:34:54 +0000 (19:34 -0800)
commit0c4a842349b27d361f1503f6437df303e1b541c9
tree6f52ce9adce2db7cdb03adf60dc0723cd2a5cc44
parent5ba53ff648e785445a32ba39112ed07e4cf588d0
signals: set_current_blocked() can use __set_current_blocked()

Cleanup.  And I think we need more cleanups, in particular
__set_current_blocked() and sigprocmask() should die.  Nobody should
ever block SIGKILL or SIGSTOP.

 - Change set_current_blocked() to use __set_current_blocked()

 - Change sys_sigprocmask() to use set_current_blocked(), this way it
   should not worry about SIGKILL/SIGSTOP.

Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
kernel/signal.c