linux-kernel - Re: Split 'flush_old_exec' into two functions - 221af7f87b97431e3ee21ce4b0e77d5411cf1549

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: <alpine.LFD.2.00.1002011036540.4206@localhost.localdomain>
Date:	Mon, 1 Feb 2010 10:41:43 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Jason Wessel <jason.wessel@...driver.com>
cc:	Michal Simek <michal.simek@...alogix.com>,
	LKML <linux-kernel@...r.kernel.org>, hpa@...or.com,
	John Williams <john.williams@...alogix.com>
Subject: Re: Split 'flush_old_exec' into two functions -
 221af7f87b97431e3ee21ce4b0e77d5411cf1549

On Mon, 1 Feb 2010, Jason Wessel wrote:
> 
> Add to the afflicted architecture list a ppc64 kernel running 32 bit
> user space apps such as a dynamically linked busybox:

The ppc issue was known - I informed the ppc people before committing, as 
they were actually using the same insane trick (along with sparc) that x86 
had to work around the bad calling conventions.

So x86, sparc and ppc were actually the main targets of the cleanup, the 
powerpc patch just wasn't ready in time. But it's merged now (got a pull 
request today), so powerpc should be ok now too (commit 94f28da84: 
"powerpc: TIF_ABI_PENDING bit removal").

The microblaze thing is different, exactly because microblaze does _not_ 
have any of that insane 32-vs-64-bit executable fiddling that this cleanup 
was all about. So microblaze I'd have expected to be totally unaffected, 
and must be about something else.

				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/