linux-kernel - Re: [PATCH v2 16/31] arm64: ELF definitions

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: <5047AE6B.6090508@tilera.com>
Date:	Wed, 5 Sep 2012 15:56:27 -0400
From:	Chris Metcalf <cmetcalf@...era.com>
To:	Arnd Bergmann <arnd@...db.de>
CC:	Catalin Marinas <catalin.marinas@....com>,
	Will Deacon <Will.Deacon@....com>,
	<linux-arch@...r.kernel.org>,
	<linux-arm-kernel@...ts.infradead.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 16/31] arm64: ELF definitions

On 8/21/2012 4:17 PM, Arnd Bergmann wrote:
> On Tuesday 21 August 2012, Catalin Marinas wrote:
>> On Thu, Aug 16, 2012 at 01:37:53PM +0100, Arnd Bergmann wrote:
>>> No, the uname output is meant to tell you about the system, not the
>>> instruction set that you are using (you already know that in compiled
>>> code).
>>
>> OK, so we assumed that compat tasks should get a uname as close as
>> possible to a 32-bit system, i.e. armv8l, for full compatibility. This
>> would allow us to run something like 32-bit Debian on an AArch64 kernel
>> without worrying about any scripts failing.
> 
> You can still do that, just boot with init="/sbin/setarch armv7 /sbin/init".
> 
>> But I can see on x86 that it always reports x86_64 even if the task is
>> x86_32.
> 
> Not just x86, the same behavior is used on powerpc, s390, mips, sparc and
> parisc. Not sure about tile though.

tile also reports "tilegx" regardless of whether the task is 64-bit or
32-bit compat.
-- 
Chris Metcalf, Tilera Corp.
http://www.tilera.com
--
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/