From: Michal Hocko <mhocko@kernel.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Hugh Dickins <hughd@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Larry Woodman <lwoodman@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] expand_downwards: don't require the gap if !vm_prev
Date: Fri, 30 Jun 2017 15:16:06 +0200 [thread overview]
Message-ID: <20170630131605.GJ22917@dhcp22.suse.cz> (raw)
In-Reply-To: <20170628175258.GA24881@redhat.com>
On Wed 28-06-17 19:52:58, Oleg Nesterov wrote:
> expand_stack(vma) fails if address < stack_guard_gap even if there is no
> vma->vm_prev. I don't think this makes sense, and we didn't do this before
> the recent commit 1be7107fbe18 ("mm: larger stack guard gap, between vmas").
> We do not need a gap in this case, any address is fine as long as
> security_mmap_addr() doesn't object.
>
> This also simplifies the code, we know that address >= prev->vm_end and
> thus underflow is not possible.
>
> Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Acked-by: Michal Hocko <mhocko@suse.com>
> ---
> mm/mmap.c | 10 +++-------
> 1 file changed, 3 insertions(+), 7 deletions(-)
>
> diff --git a/mm/mmap.c b/mm/mmap.c
> index 8e07976..5a8bd97 100644
> --- a/mm/mmap.c
> +++ b/mm/mmap.c
> @@ -2310,7 +2310,6 @@ int expand_downwards(struct vm_area_struct *vma,
> {
> struct mm_struct *mm = vma->vm_mm;
> struct vm_area_struct *prev;
> - unsigned long gap_addr;
> int error;
>
> address &= PAGE_MASK;
> @@ -2319,14 +2318,11 @@ int expand_downwards(struct vm_area_struct *vma,
> return error;
>
> /* Enforce stack_guard_gap */
> - gap_addr = address - stack_guard_gap;
> - if (gap_addr > address)
> - return -ENOMEM;
I thought this was an underflow protection. address might be still above
min_mmap address while gap_addr can underflow, that would mean that we
might not detect a mapping in that range, but
> prev = vma->vm_prev;
> - if (prev && prev->vm_end > gap_addr) {
> - if (!(prev->vm_flags & VM_GROWSDOWN))
> + /* Check that both stack segments have the same anon_vma? */
> + if (prev && !(prev->vm_flags & VM_GROWSDOWN)) {
> + if (address - prev->vm_end < stack_guard_gap)
this would handle that case properly so the problem wouldn't happen.
> return -ENOMEM;
> - /* Check that both stack segments have the same anon_vma? */
> }
>
> /* We must make sure the anon_vma is allocated. */
> --
> 2.5.0
>
>
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2017-06-30 13:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 17:52 [PATCH 0/1] " Oleg Nesterov
2017-06-28 17:52 ` [PATCH 1/1] " Oleg Nesterov
2017-06-30 13:16 ` Michal Hocko [this message]
2017-06-28 23:26 ` [PATCH 0/1] " Linus Torvalds
2017-06-29 15:19 ` Oleg Nesterov
2017-06-29 18:21 ` Linus Torvalds
2017-06-29 18:55 ` Oleg Nesterov
2017-06-29 19:00 ` Linus Torvalds
2017-06-30 13:24 ` Michal Hocko
2017-06-30 17:08 ` Linus Torvalds
2017-06-30 17:26 ` Michal Hocko
2017-06-30 17:48 ` Linus Torvalds
2017-07-03 15:49 ` Michal Hocko
2017-07-03 16:30 ` Linus Torvalds
2017-07-03 16:54 ` Michal Hocko
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=20170630131605.GJ22917@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lwoodman@redhat.com \
--cc=oleg@redhat.com \
--cc=torvalds@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®