linux-kernel - Re: 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 05 Mar 2008 22:45:15 +0100
From:	Aurelien Jarno <aurelien@...el32.net>
To:	Richard Guenther <richard.guenther@...il.com>
CC:	Joe Buck <Joe.Buck@...opsys.com>, Michael Matz <matz@...e.de>,
	Jan Hubicka <hubicka@....cz>, "H. Peter Anvin" <hpa@...or.com>,
	linux-kernel@...r.kernel.org, gcc@....gnu.org
Subject: Re: RELEASE BLOCKER: Linux doesn't follow x86/x86-64 ABI wrt direction
 flag

Richard Guenther a écrit :
> On Wed, Mar 5, 2008 at 10:20 PM, Joe Buck <Joe.Buck@...opsys.com> wrote:
>>
>>  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.
> 
> We didn't yet run into this issue and build openSUSE with 4.3 since more than
> three month.
> 

The problem can be easily reproduced by using a glibc built with gcc
4.3, with SBCL (the gcc version doesn't matter). The signal handler in
SBCL calls sigemptyset() which uses memset().


-- 
  .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   aurel32@...ian.org         | aurelien@...el32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net
--
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/