linux-kernel - RELEASE BLOCKER: Linux doesn't follow x86/x86-64 ABI wrt direction flag

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: <20080305212005.GC17267@synopsys.com>
Date:	Wed, 5 Mar 2008 13:20:05 -0800
From:	Joe Buck <Joe.Buck@...opsys.COM>
To:	Michael Matz <matz@...e.de>
Cc:	Jan Hubicka <hubicka@....cz>,
	Aurelien Jarno <aurelien@...el32.net>,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
	gcc@....gnu.org
Subject: RELEASE BLOCKER: Linux doesn't follow x86/x86-64 ABI wrt direction flag



On Wed, 5 Mar 2008, Jan Hubicka wrote:
> > Linux kernel is disabling red zone and use kernel code model, yet the 
> > ABI is not going to be adjusted for that.
> > 
> > This is resonably easy to fix on kernel side in signal handling, or by
> > removing std usage completely

On Wed, Mar 05, 2008 at 10:02:07PM +0100, Michael Matz wrote:
> That is true.  But it requires updating the kernel to a fixed one if you 
> want to run your programs compiled by 4.3 :-/  Not something we'd like to 
> demand.

I changed the title just for emphasis.

I think that we can't ship 4.3.0 if signal handlers on x86/x86_64
platforms for both Linux and BSD systems will mysteriously (to the users)
fail, and it doesn't matter whose fault it is.


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