linux-kernel - Re: [PATCH 00/18] Make common x86 arch area for i386 and x86_64

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.0703150919021.3816@woody.linux-foundation.org>
Date:	Thu, 15 Mar 2007 09:23:24 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Andi Kleen <andi@...stfloor.org>
cc:	Martin Bligh <mbligh@...igh.org>, Ingo Molnar <mingo@...e.hu>,
	Steven Rostedt <rostedt@...dmis.org>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Chris Wright <chrisw@...s-sol.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Glauber de Oliveira Costa <glommer@...il.com>
Subject: Re: [PATCH 00/18] Make common x86 arch area for i386 and x86_64 -
 Take 2



On Thu, 15 Mar 2007, Andi Kleen wrote:

> > That's *exactly* what the patches do (except it's called "arch/x86", which 
> > is clearly the best option - please don't use "ia" _anywhere_ except for 
> > "ia64", since that's the only architecture that is really "intel 
> > architecture").
> 
> And i860 @)

Yeah, well (and the i960).. I don't think it's very likely that we'll ever 
support that in the kernel ;)

(There are others. i432 is the really *classic* intel architecture. It was 
such a spectacular failure that it's still remembered today, even though 
it was never actually used).

> Well I just see a lot of pain from these patches but I doubt 
> they will avoid any bugs. If people don't compile test both
> archs they will always likely break on another. There are lots
> of subtle dependencies that are not expressed in the pathname
> even after this intrusive operation (e.g. in the includes).

Well, we'veliterally had bugs because people who modified i386 files 
didn't even *realize* that they were also used on x86-64. 

I do agree that we'd need to look at do the same thing for include files, 
for the same reason. 

			Linus
-
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/