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: <6dc9ffc80803060743h502fc96bj6117ef87a8555c3a@mail.gmail.com>
Date:	Thu, 6 Mar 2008 07:43:16 -0800
From:	"H.J. Lu" <hjl.tools@...il.com>
To:	NightStrike <nightstrike@...il.com>
Cc:	"Olivier Galibert" <galibert@...ox.com>,
	"H. Peter Anvin" <hpa@...or.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

I agree with it. There is no  right or wrong here Let's start from
scratch and figure out
what is the best way to handle this, assuming we are defining a new psABI.

H.J.
On Thu, Mar 6, 2008 at 7:37 AM, NightStrike <nightstrike@...il.com> wrote:
>
> On 3/6/08, Olivier Galibert <galibert@...ox.com> wrote:
>  > On Wed, Mar 05, 2008 at 05:12:07PM -0800, H. Peter Anvin wrote:
>  > > It's a kernel bug, and it needs to be fixed.
>  >
>  > I'm not convinced.  It's been that way for 15 years, it's that way in
>  > the BSD kernels, at that point it's a feature.  The bug is in the
>  > documentation, nowhere else.  And in gcc for blindly trusting the
>  > documentation.
>
>  The issue should not be evaluated as: "It's always been that way,
>  therefore, it's right."  Instead, it should be: "What's the right way
>  to do it?"
>
>  You don't just change documentation because no existing code meets the
>  requirement -- UNLESS -- the non-conforming code is actually the right
>  way to do things.
>
--
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/