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: Windows password security audit tool. GUI, reports in PDF.

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

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

On Wed, Mar 5, 2008 at 10:34 PM, H. Peter Anvin <hpa@...or.com> wrote:
> Richard Guenther wrote:
>  >
>  > We didn't yet run into this issue and build openSUSE with 4.3 since more than
>  > three month.
>  >
>
>  Well, how often do you take a trap inside an overlapping memmove()?

Right.  So this problem is over-exaggerated.  It's not like
"any binary you create on that system will be broken on any
other existing system."

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