lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 15 Feb 2012 09:43:54 +0100 From: Jesper Nilsson <jesper.nilsson@...s.com> To: Matt Fleming <matt@...sole-pimps.org> Cc: "linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>, Oleg Nesterov <oleg@...hat.com>, Andrew Morton <akpm@...ux-foundation.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Matt Fleming <matt.fleming@...el.com>, Mikael Starvik <starvik@...s.com>, linux-cris-kernel <linux-cris-kernel@...s.com> Subject: Re: [PATCH 08/40] cris: Use set_current_blocked() and block_sigmask() On Tue, Feb 14, 2012 at 12:40:41PM +0100, Matt Fleming wrote: > From: Matt Fleming <matt.fleming@...el.com> > > As described in e6fa16ab ("signal: sigprocmask() should do > retarget_shared_pending()") the modification of current->blocked is > incorrect as we need to check whether the signal we're about to block > is pending in the shared queue. > > Also, use the new helper function introduced in commit 5e6292c0f28f > ("signal: add block_sigmask() for adding sigmask to current->blocked") > which centralises the code for updating current->blocked after > successfully delivering a signal and reduces the amount of duplicate > code across architectures. In the past some architectures got this > code wrong, so using this helper function should stop that from > happening again. > > Cc: Oleg Nesterov <oleg@...hat.com> > Cc: Mikael Starvik <starvik@...s.com> > Cc: Jesper Nilsson <jesper.nilsson@...s.com> Acked-by: Jesper Nilsson <jesper.nilsson@...s.com> > Cc: linux-cris-kernel@...s.com > Signed-off-by: Matt Fleming <matt.fleming@...el.com> /^JN - Jesper Nilsson -- Jesper Nilsson -- jesper.nilsson@...s.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists