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: <6dc9ffc80803060934q3df9b5b5gf336b1ed0af16820@mail.gmail.com>
Date:	Thu, 6 Mar 2008 09:34:35 -0800
From:	"H.J. Lu" <hjl.tools@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	"Jakub Jelinek" <jakub@...hat.com>,
	NightStrike <nightstrike@...il.com>,
	"Olivier Galibert" <galibert@...ox.com>,
	"Chris Lattner" <clattner@...le.com>,
	"Michael Matz" <matz@...e.de>,
	"Richard Guenther" <richard.guenther@...il.com>,
	"Joe Buck" <Joe.Buck@...opsys.com>, "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 Thu, Mar 6, 2008 at 9:17 AM, H. Peter Anvin <hpa@...or.com> wrote:
> H.J. Lu wrote:
>  >>
>  >>  Not a fix, an (optional) workaround for a system bug.
>  >
>  > So that is the bug in the Linux kernel. Since fixing kernel is much easier
>  > than providing a workaround in compilers, I think kernel should be fixed
>  > and no need for icc/gcc fix.
>  >
>
>  The problem is, you're going to have to be able to produce binaries
>  compatible with old kernels for a *long* time for come.  Are you
>  honestly saying you'll tell those people "use gcc 4.2 or earlier"?  If
>  so, I think most distros will have to freeze gcc for the next several years.
>

Icc has been following psABI for years on Linux and it doesn't stop people
using icc on Linux.  On the other hand, it may be a good idea to provide a
workaround in gcc and enables it by default.  OSVs can fix thekernel and
disable it by default.

We can even issue a message whenever the workaround is used.

H.J.
--
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/