Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Tue, 20 Feb 2018 14:46:23 +0100
From: Michal Hocko <>
To: Kees Cook <>
Cc: Andrew Morton <>,
	Linus Torvalds <>,
	Ben Hutchings <>, Willy Tarreau <>,
	Hugh Dickins <>, Oleg Nesterov <>,
	"Jason A. Donenfeld" <>,
	Rik van Riel <>, Laura Abbott <>,
	Greg KH <>, Andy Lutomirski <>,,,,
Subject: Re: [RESEND][PATCH 0/3] exec: Pin stack limit during exec

On Wed 14-02-18 12:06:33, Kees Cook wrote:
> Attempts to solve problems with the stack limit changing during exec
> continue to be frustrated[1][2]. In addition to the specific issues around
> the Stack Clash family of flaws, Andy Lutomirski pointed out[3] other
> places during exec where the stack limit is used and is assumed to be
> unchanging. Given the many places it gets used and the fact that it can be
> manipulated/raced via setrlimit() and prlimit(), I think the only way to
> handle this is to move away from the "current" view of the stack limit and
> instead attach it to the bprm, and plumb this down into the functions that
> need to know the stack limits. This series implements the approach.
> Neither I nor 0-day have found issues with this series, so I'd like to
> get it into -mm for further testing.

Sorry, for the late response. All three patches make sense to me.
finalize_exec could see a much better documentation and explain what is
the semantic.

Anyway, feel free to add
Acked-by: Michal Hocko <>
Michal Hocko

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.