linux-kernel - Re: 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: <Pine.LNX.4.64.0803052158270.20583@wotan.suse.de>
Date:	Wed, 5 Mar 2008 22:02:07 +0100 (CET)
From:	Michael Matz <matz@...e.de>
To:	Jan Hubicka <hubicka@....cz>
Cc:	Joe Buck <Joe.Buck@...opsys.COM>,
	Aurelien Jarno <aurelien@...el32.net>,
	"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
	gcc@....gnu.org
Subject: Re: Linux doesn't follow x86/x86-64 ABI wrt direction flag

Hi,

On Wed, 5 Mar 2008, Jan Hubicka wrote:

> Kernels almost never follow ABI used by applications to last detail. 

But we aren't talking about the ABI the kernel uses internally, but about 
what is exposed to user-space via signal handlers.  _That_ part needs to 
be followed, and if it isn't it's a serious problem we somehow have to 
hack around.

> 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

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.

Ciao,
Michael.
--
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/