linux-kernel - Re: [PATCH 02/30] x86-64: Use explicit sizes in sigcontext.h, prepare for x32

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: <4F559FB9.9040008@kernel.org>
Date:	Mon, 05 Mar 2012 21:25:13 -0800
From:	"H. Peter Anvin" <hpa@...nel.org>
To:	Arnd Bergmann <arnd@...db.de>
CC:	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	mingo@...nel.org, tglx@...utronix.de, akpm@...ux-foundation.org,
	hjl.tools@...il.com
Subject: Re: [PATCH 02/30] x86-64: Use explicit sizes in sigcontext.h, prepare
 for x32

On 02/23/2012 06:33 PM, H. Peter Anvin wrote:
> On 02/22/2012 01:23 PM, Arnd Bergmann wrote:
>>
>> I'd say we should fix at least the ones that are easy to spot because
>> they already use compat_u64 or have an #ifdef CONFIG_X86_64 in compat
>> code. I've looked at everything I could find that fits into that category
>> and found only two locations. My expectation is that all other data
>> structures that would fall into this category are already broken
>> for 32 bit emulation on x86.
>>
>> Signed-off-by: Arnd Bergmann <arnd@...db.de>
>>
> 
> Would you mind sending these as patches to the respective maintainers?
> Since they don't depend on the x32 patchset per se it's probably the
> best way to handle this.
> 
> Feel free to include my Acked-by: H. Peter Anvin <hpa@...or.com>.
> 

Ping?

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