linux-kernel - Re: [stable] [29/93] fs/exec.c: restrict initial stack space expansion to rlimit

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: <9355.1266957761@neuling.org>
Date:	Wed, 24 Feb 2010 07:42:41 +1100
From:	Michael Neuling <mikey@...ling.org>
To:	Greg KH <greg@...ah.com>
cc:	Greg KH <gregkh@...e.de>, Serge Hallyn <serue@...ibm.com>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	stable@...nel.org, Anton Blanchard <anton@...ba.org>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	Oleg Nesterov <oleg@...hat.com>,
	Americo Wang <xiyou.wangcong@...il.com>,
	akpm@...ux-foundation.org, James Morris <jmorris@...ei.org>,
	torvalds@...ux-foundation.org, stable-review@...nel.org,
	alan@...rguk.ukuu.org.uk
Subject: Re: [stable] [29/93] fs/exec.c: restrict initial stack space expansion to rlimit

In message <20100223153412.GB4275@...ah.com> you wrote:
> On Sun, Feb 21, 2010 at 05:42:44PM +1100, Michael Neuling wrote:
> > In message <20100219163238.671588178@....kroah.org> you wrote:
> > > 2.6.32-stable review patch.  If anyone has any objections, please let us 
know
> > .
> > > 
> > > ------------------
> > > 
> > > From: Michael Neuling <mikey@...ling.org>
> > > 
> > > commit 803bf5ec259941936262d10ecc84511b76a20921 upstream.
> > > 
> > > When reserving stack space for a new process, make sure we're not
> > > attempting to expand the stack by more than rlimit allows.
> > 
> > This breaks UML, so you also need to take this also:
> > 
> >   http://patchwork.kernel.org/patch/79365/
> > 
> > It's in akpm's tree only so far.
> 
> As I can't take patches that are not in Linus's tree, can you let
> stable@...nel.org know the git commit id of the patch when it goes into
> Linus's tree, and then I will apply it to the next .32-stable release?

No problems.  Actually, Linus took it over night.  SHA1 is
a17e18790a8c47113a73139d54a375dc9ccd8f08 "fs/exec.c: fix initial stack
reservation"

I'll send a note to stable now.

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