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: Tue, 23 Aug 2011 08:04:51 +0200 From: Martin Schwidefsky <schwidefsky@...ibm.com> To: Matt Fleming <matt@...sole-pimps.org> Cc: Oleg Nesterov <oleg@...hat.com>, linux-kernel@...r.kernel.org, Heiko Carstens <heiko.carstens@...ibm.com> Subject: Re: [PATCH 26/43] [S390]: Use block_sigmask() On Fri, 19 Aug 2011 17:46:42 +0100 Matt Fleming <matt@...sole-pimps.org> wrote: > From: Matt Fleming <matt.fleming@...el.com> > > Use the new helper function block_sigmask() 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: Martin Schwidefsky <schwidefsky@...ibm.com> > Cc: Heiko Carstens <heiko.carstens@...ibm.com> > Signed-off-by: Matt Fleming <matt.fleming@...el.com> > --- > > This patch depends on "[PATCH 01/43] signal: Add block_sigmask() for > adding sigmask to current->blocked" so they need to go through the > same tree but this patch would benefit from some maintainer ACK's. > > arch/s390/kernel/compat_signal.c | 6 +----- > arch/s390/kernel/signal.c | 6 +----- > 2 files changed, 2 insertions(+), 10 deletions(-) Identical code replacement and compiles fine. Acked-by: Martin Schwidefsky <schwidefsky@...ibm.com> -- blue skies, Martin. "Reality continues to ruin my life." - Calvin. -- 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