From: Oleg Nesterov <oleg@redhat.com>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [mm] 1be7107fbe: kernel_BUG_at_mm/mmap.c
Date: Wed, 21 Jun 2017 21:33:39 +0200 [thread overview]
Message-ID: <20170621193338.GA29222@redhat.com> (raw)
In-Reply-To: <CA+55aFxzdtZ787snPhLhU8+2xUHKd74Som82yRCiFSQVXCNFhA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1539 bytes --]
On 06/21, Linus Torvalds wrote:
>
> Hugh, Michal - I also merged Helge's drop-up cleanup, is there
> anything I've missed? I think Oleg had something, but I can't recall
> right now, and I might just have missed it.
Well, I meant, perhaps we need a bit more changes to ensure that a new
GROWSDOWN vma can't come without a gap below. But this is really minor,
we can do this later even if I am right.
However, there is another regression reported by Cyrill. Fixed by the
patch below.
And yes, I think this check should either go away, or we need to make
it more clever.
In short, the vma created by mmap(MAP_GROWSDOWN) does not grow down
automatically, because of this check.
This worked before, because with the stack guard page at ->vm_start
__do_page_fault() hits this expand-stack path only if the stack grows
by more than PAGE_SIZE, now it is called every time. I'll send the
patch tomorrow if nobody else does this before.
Oleg.
---
diff --git a/arch/x86/mm/fault.c b/arch/x86/mm/fault.c
index 8ad91a0..edc5d68 100644
--- a/arch/x86/mm/fault.c
+++ b/arch/x86/mm/fault.c
@@ -1416,7 +1416,7 @@ __do_page_fault(struct pt_regs *regs, unsigned long error_code,
* and pusha to work. ("enter $65535, $31" pushes
* 32 pointers and then decrements %sp by 65535.)
*/
- if (unlikely(address + 65536 + 32 * sizeof(unsigned long) < regs->sp)) {
+if (0) if (unlikely(address + 65536 + 32 * sizeof(unsigned long) < regs->sp)) {
bad_area(regs, error_code, address);
return;
}
WARNING: multiple messages have this Message-ID (diff)
From: Oleg Nesterov <oleg@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Hugh Dickins <hughd@google.com>,
kernel test robot <xiaolong.ye@intel.com>,
Michal Hocko <mhocko@suse.com>,
LKML <linux-kernel@vger.kernel.org>, LKP <lkp@01.org>
Subject: Re: [lkp-robot] [mm] 1be7107fbe: kernel_BUG_at_mm/mmap.c
Date: Wed, 21 Jun 2017 21:33:39 +0200 [thread overview]
Message-ID: <20170621193338.GA29222@redhat.com> (raw)
In-Reply-To: <CA+55aFxzdtZ787snPhLhU8+2xUHKd74Som82yRCiFSQVXCNFhA@mail.gmail.com>
On 06/21, Linus Torvalds wrote:
>
> Hugh, Michal - I also merged Helge's drop-up cleanup, is there
> anything I've missed? I think Oleg had something, but I can't recall
> right now, and I might just have missed it.
Well, I meant, perhaps we need a bit more changes to ensure that a new
GROWSDOWN vma can't come without a gap below. But this is really minor,
we can do this later even if I am right.
However, there is another regression reported by Cyrill. Fixed by the
patch below.
And yes, I think this check should either go away, or we need to make
it more clever.
In short, the vma created by mmap(MAP_GROWSDOWN) does not grow down
automatically, because of this check.
This worked before, because with the stack guard page at ->vm_start
__do_page_fault() hits this expand-stack path only if the stack grows
by more than PAGE_SIZE, now it is called every time. I'll send the
patch tomorrow if nobody else does this before.
Oleg.
---
diff --git a/arch/x86/mm/fault.c b/arch/x86/mm/fault.c
index 8ad91a0..edc5d68 100644
--- a/arch/x86/mm/fault.c
+++ b/arch/x86/mm/fault.c
@@ -1416,7 +1416,7 @@ __do_page_fault(struct pt_regs *regs, unsigned long error_code,
* and pusha to work. ("enter $65535, $31" pushes
* 32 pointers and then decrements %sp by 65535.)
*/
- if (unlikely(address + 65536 + 32 * sizeof(unsigned long) < regs->sp)) {
+if (0) if (unlikely(address + 65536 + 32 * sizeof(unsigned long) < regs->sp)) {
bad_area(regs, error_code, address);
return;
}
next prev parent reply other threads:[~2017-06-21 19:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 2:35 [lkp-robot] [mm] 1be7107fbe: kernel_BUG_at_mm/mmap.c kernel test robot
2017-06-21 2:35 ` kernel test robot
2017-06-21 2:41 ` Hugh Dickins
2017-06-21 2:41 ` Hugh Dickins
2017-06-21 18:29 ` Linus Torvalds
2017-06-21 18:29 ` Linus Torvalds
2017-06-21 19:33 ` Oleg Nesterov [this message]
2017-06-21 19:33 ` Oleg Nesterov
2017-06-21 19:39 ` Linus Torvalds
2017-06-21 19:39 ` Linus Torvalds
2017-06-21 20:27 ` Oleg Nesterov
2017-06-21 20:27 ` Oleg Nesterov
2017-06-21 20:30 ` Linus Torvalds
2017-06-21 20:30 ` Linus Torvalds
2017-06-21 20:56 ` Oleg Nesterov
2017-06-21 20:56 ` Oleg Nesterov
2017-06-21 22:19 ` Linus Torvalds
2017-06-21 22:19 ` Linus Torvalds
2017-06-22 1:07 ` Hugh Dickins
2017-06-22 1:07 ` Hugh Dickins
2017-06-22 10:58 ` Dmitry Safonov
2017-06-22 10:58 ` Dmitry Safonov
2017-06-22 15:16 ` Oleg Nesterov
2017-06-22 15:16 ` Oleg Nesterov
2017-06-22 18:04 ` Hugh Dickins
2017-06-22 18:04 ` Hugh Dickins
2017-06-22 20:51 ` Oleg Nesterov
2017-06-22 20:51 ` Oleg Nesterov
2017-06-22 4:23 ` Hugh Dickins
2017-06-22 4:23 ` Hugh Dickins
2017-06-21 19:39 ` Hugh Dickins
2017-06-21 19:39 ` Hugh Dickins
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=20170621193338.GA29222@redhat.com \
--to=oleg@redhat.com \
--cc=lkp@lists.01.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 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.