linux-kernel - Re: [RFC] x86, fpu: unify signal handling code paths for x86 and x86

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4FDA8D3B.5020107@zytor.com>
Date:	Thu, 14 Jun 2012 18:17:47 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Suresh Siddha <suresh.b.siddha@...el.com>
CC:	Hans Rosenfeld <hans.rosenfeld@....com>,
	Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel <linux-kernel@...r.kernel.org>, tglx@...utronix.de,
	robert.richter@....com, andreas.herrmann3@....com
Subject: Re: [RFC] x86, fpu: unify signal handling code paths for x86 and
 x86_64 kernels

On 06/14/2012 06:16 PM, Suresh Siddha wrote:
> On Thu, 2012-06-14 at 18:13 -0700, H. Peter Anvin wrote:
>> On 06/14/2012 06:07 PM, Suresh Siddha wrote:
>>> Ok. Fix for the existing mainline code appended. Can you queue this
>>> separately?
>>
>> Your unification patch still needs this too, though, right?
>>
> 
> Yes, that will be new code. Not for 3.5 though. So will send it
> separately, when I send the non-RFC version of the signal unification
> patches.
> 

Thanks.  Actually what would be better is to just base that patch on top
of tip:x86/urgent unless it is already merged into mainline by then.

	-hpa


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