[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1498230808.13083.29.camel@redhat.com>
Date: Fri, 23 Jun 2017 11:13:28 -0400
From: Rik van Riel <riel@...hat.com>
To: Ingo Molnar <mingo@...nel.org>
Cc: linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
will.deacon@....com, danielmicay@...il.com,
benh@...nel.crashing.org, hughd@...gle.com,
Linus Torvalds <torvalds@...ux-foundation.org>,
Michal Hocko <mhocko@...e.com>,
Dave Jones <davej@...emonkey.org.uk>,
Oleg Nesterov <oleg@...hat.com>
Subject: Re: [PATCH 0/3] properly account for stack randomization and guard
gap
On Fri, 2017-06-23 at 10:35 +0200, Ingo Molnar wrote:
> * riel@...hat.com <riel@...hat.com> wrote:
>
> > When RLIMIT_STACK is larger than the minimum gap enforced by
> > mmap_base(), it is possible for the kernel to place the mmap
> > area where the stack wants to grow, resulting in the stack
> > not being able to use the space that should have been allocated
> > to it through RLIMIT_STACK.
> >
> > This series ensures that x86, ARM64, and PPC have at least
> > RLIMIT_STACK + stack randomization + the stack guard gap
> > space available for the stack.
> >
> > s390 seems to be ok. I have not checked other architectures.
>
> x86 patch LGTM:
>
> Acked-by: Ingo Molnar <mingo@...nel.org>
>
> ... but I suspect this wants to go via -mm or Linus directly?
I believe Andrew picked it up yesterday.
Powered by blists - more mailing lists