linux-kernel - [PATCH 0/2] block_sigmask() helper function

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 21 Dec 2011 18:46:59 +0000
From:	Matt Fleming <matt@...sole-pimps.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	"David S. Miller" <davem@...emloft.net>,
	linux-kernel@...r.kernel.org, Oleg Nesterov <oleg@...hat.com>,
	Matt Fleming <matt.fleming@...el.com>
Subject: [PATCH 0/2] block_sigmask() helper function

From: Matt Fleming <matt.fleming@...el.com>

Hi Andrew,

Oleg doesn't have a repo on kernel.org yet and suggested that you
might take these patches through your -mm tree? Ideally I'd like to
get these two in for the 3.3 merge window because I've got a bunch of
other patches that can go through the respective maintainers' trees
once these two have been merged.

These two patches have been posted before (along with the other 40)
but I attempted to get them all merged in one go, which didn't really
work. The original thread is here,

      https://lkml.org/lkml/2011/8/19/411

Matt Fleming (2):
  sparc: Make SA_NOMASK a synonym of SA_NODEFER
  signal: Add block_sigmask() for adding sigmask to current->blocked

 arch/sparc/include/asm/signal.h |    3 ++-
 arch/x86/kernel/signal.c        |    6 +-----
 include/linux/signal.h          |    1 +
 kernel/signal.c                 |   21 +++++++++++++++++++++
 4 files changed, 25 insertions(+), 6 deletions(-)

-- 
1.7.4.4

--
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/