| From | Herton Ronaldo Krzesinski <> | Subject | [PATCH 215/222] signals: sys_ssetmask() uses uninitialized newmask | Date | Wed, 16 Jan 2013 13:56:55 -0200 |
| |
3.5.7.3 -stable review patch. If anyone has any objections, please let me know.
------------------
From: Oleg Nesterov <oleg@redhat.com>
commit 5ba53ff648e785445a32ba39112ed07e4cf588d0 upstream.
Commit 77097ae503b1 ("most of set_current_blocked() callers want SIGKILL/SIGSTOP removed from set") removed the initialization of newmask by accident, causing ltp to complain like this:
ssetmask01 1 TFAIL : sgetmask() failed: TEST_ERRNO=???(0): Success
Restore the proper initialization.
Reported-and-tested-by: CAI Qian <caiqian@redhat.com> Signed-off-by: Oleg Nesterov <oleg@redhat.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Herton Ronaldo Krzesinski <herton.krzesinski@canonical.com> --- kernel/signal.c | 1 + 1 file changed, 1 insertion(+)
diff --git a/kernel/signal.c b/kernel/signal.c index 6771027..e9d3270 100644 --- a/kernel/signal.c +++ b/kernel/signal.c @@ -3215,6 +3215,7 @@ SYSCALL_DEFINE1(ssetmask, int, newmask) int old = current->blocked.sig[0]; sigset_t newset; + siginitset(&newset, newmask); set_current_blocked(&newset); return old; -- 1.7.9.5
|