linux-kernel - Re: [stable] [PATCH] Fix 'flush_old_exec()/setup_new

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: <87iqachtgh.fsf@turtle.gmx.de>
Date:	Fri, 05 Feb 2010 11:23:26 +0100
From:	Sven Joachim <svenjoac@....de>
To:	Ben Hutchings <ben@...adent.org.uk>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Greg KH <greg@...ah.com>, stable-review@...nel.org,
	stable@...nel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [stable] [PATCH] Fix 'flush_old_exec()/setup_new_exec()' split

On 2010-02-04 23:25 +0100, Ben Hutchings wrote:

> In a Debian initramfs, /init is a script interpreted by /bin/sh.

Yes, I tested without an initramfs though.  The crash happens actually
before init is run.

> I've now tested i386 userland on an x86_64 kernel with all the relevant
> patches on top of 2.6.32.7:
>
> fdpic-respect-pt_gnu_stack-exec-protection-markings-when-creating-nommu-stack.patch
> split-flush_old_exec-into-two-functions.patch
> sparc-tif_abi_pending-bit-removal.patch
> x86-get-rid-of-the-insane-tif_abi_pending-bit.patch
> fix-flush_old_exec-setup_new_exec-split.patch
> powerpc-tif_abi_pending-bit-removal.patch
>
> This works perfectly, so far as I can see.

It seems so.  The faulty patch is actually the cherry-pick of commit
28f6aeea (net: restore ip source validation), reverting that leads to a
kernel that runs fine.  And this has nothing to do with 64-bit vs
32-bit.

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