From: Linus Torvalds <torvalds@linux-foundation.org>
To: Oleg Nesterov <oleg@redhat.com>
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 13:30:28 -0700 [thread overview]
Message-ID: <CA+55aFyupxx0K6SCi5_vd5nt0FmUYrYGF6yB+k9F+9zbgMwsiQ@mail.gmail.com> (raw)
In-Reply-To: <20170621202751.GA29638@redhat.com>
On Wed, Jun 21, 2017 at 1:27 PM, Oleg Nesterov <oleg@redhat.com> wrote:
>
> Now __do_page_fault() tries to expand the stack itself, and this check
> fails.
But we want that check to trigger and cause the access to fail.
Accessing the stack below the stack pointer is wrong.
Do you have a pointer to the report for this regression? I must have missed it.
Linus
WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [mm] 1be7107fbe: kernel_BUG_at_mm/mmap.c
Date: Wed, 21 Jun 2017 13:30:28 -0700 [thread overview]
Message-ID: <CA+55aFyupxx0K6SCi5_vd5nt0FmUYrYGF6yB+k9F+9zbgMwsiQ@mail.gmail.com> (raw)
In-Reply-To: <20170621202751.GA29638@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 390 bytes --]
On Wed, Jun 21, 2017 at 1:27 PM, Oleg Nesterov <oleg@redhat.com> wrote:
>
> Now __do_page_fault() tries to expand the stack itself, and this check
> fails.
But we want that check to trigger and cause the access to fail.
Accessing the stack below the stack pointer is wrong.
Do you have a pointer to the report for this regression? I must have missed it.
Linus
next prev parent reply other threads:[~2017-06-21 20:30 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
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 [this message]
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=CA+55aFyupxx0K6SCi5_vd5nt0FmUYrYGF6yB+k9F+9zbgMwsiQ@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mhocko@suse.com \
--cc=oleg@redhat.com \
--cc=xiaolong.ye@intel.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.