linux-kernel - Re: Linux 3.3-rc4

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CA+55aFzcWjPrK4csbThuGimt6bHC+bcgFhj-r8d3M1MxhN_HKg@mail.gmail.com>
Date:	Mon, 20 Feb 2012 21:21:06 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Ian Kent <raven@...maw.net>
Cc:	David Miller <davem@...emloft.net>, thomas@...3r.de,
	linux-kernel@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>
Subject: Re: Linux 3.3-rc4

On Mon, Feb 20, 2012 at 9:06 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> So it really is limited to only x86.

Oh, and if people really are using "uname()" to figure out that they
are running a 64-bit kernel, then we should probably make uname() use
"is_compat_task()" instead of checking the PER_LINUX32 personality.

So we already do have support for returning a different machine-name
to 32-bit binaries, but it uses the "personality" thing that nobody
cares about, rather than the compat layer. Looks like purely
historical reasons.

               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/