From: Rik van Riel <riel@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
will.deacon@arm.com, danielmicay@gmail.com,
benh@kernel.crashing.org, hughd@google.com,
Linus Torvalds <torvalds@linux-foundation.org>,
Michal Hocko <mhocko@suse.com>,
Dave Jones <davej@codemonkey.org.uk>,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH 0/3] properly account for stack randomization and guard gap
Date: Fri, 23 Jun 2017 11:13:28 -0400 [thread overview]
Message-ID: <1498230808.13083.29.camel@redhat.com> (raw)
In-Reply-To: <20170623083521.f62me7efrm4ygawq@gmail.com>
On Fri, 2017-06-23 at 10:35 +0200, Ingo Molnar wrote:
> * riel@redhat.com <riel@redhat.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@kernel.org>
>
> ... but I suspect this wants to go via -mm or Linus directly?
I believe Andrew picked it up yesterday.
prev parent reply other threads:[~2017-06-23 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 20:00 [PATCH 0/3] properly account for stack randomization and guard gap riel
2017-06-22 20:00 ` [PATCH 1/3] x86/mmap: properly account for stack randomization in mmap_base riel
2017-06-22 20:00 ` [PATCH 2/3] arm64/mmap: " riel
2017-06-22 20:00 ` [PATCH 3/3] powerpc,mmap: " riel
2017-06-23 8:35 ` [PATCH 0/3] properly account for stack randomization and guard gap Ingo Molnar
2017-06-23 15:13 ` Rik van Riel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1498230808.13083.29.camel@redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=danielmicay@gmail.com \
--cc=davej@codemonkey.org.uk \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.