Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 12 Jul 2016 07:57:31 -0400
From: Brian Gerst <>
To: Andy Lutomirski <>
Cc: "the arch/x86 maintainers" <>, 
	Linux Kernel Mailing List <>, linux-arch <>, 
	Borislav Petkov <>, Nadav Amit <>, Kees Cook <>, 
	"" <>, 
	Linus Torvalds <>, Josh Poimboeuf <>, 
	Jann Horn <>, Heiko Carstens <>, 
	Richard Henderson <>, Ivan Kokshaysky <>, 
	Matt Turner <>, Tony Luck <>, 
	Fenghua Yu <>, Michal Simek <>, 
	Benjamin Herrenschmidt <>, Paul Mackerras <>, 
	Michael Ellerman <>, Yoshinori Sato <>, 
	Rich Felker <>, "David S. Miller" <>, 
	Chris Metcalf <>, Peter Zijlstra <>, 
	Borislav Petkov <>, Dmitry Safonov <>, 
	Andrew Morton <>,,,,,
Subject: Re: [PATCH v5 18/32] signal: Consolidate {TS,TLF}_RESTORE_SIGMASK code

On Mon, Jul 11, 2016 at 4:53 PM, Andy Lutomirski <> wrote:
> In general, there's no need for the "restore sigmask" flag to live in
> ti->flags.  alpha, ia64, microblaze, powerpc, sh, sparc (64-bit only),
> tile, and x86 use essentially identical alternative implementations,
> placing the flag in ti->status.
> Replace those optimized implementations with an equally good common
> implementation that stores it in a bitfield in struct task_struct
> and drop the custom implementations.
> Additional architectures can opt in by removing their

There is a small typo in the subject, should be "signal: Consolidate

Brian Gerst

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.