mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hugh Dickins <hughd@google.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Hugh Dickins <hughd@google.com>,
	kernel test robot <xiaolong.ye@intel.com>,
	Oleg Nesterov <oleg@redhat.com>, Michal Hocko <mhocko@suse.com>,
	Willy Tarreau <w@1wt.eu>, 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 12:39:52 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LSU.2.11.1706211238180.17033@eggly.anvils> (raw)
In-Reply-To: <CA+55aFxzdtZ787snPhLhU8+2xUHKd74Som82yRCiFSQVXCNFhA@mail.gmail.com>

On Wed, 21 Jun 2017, Linus Torvalds wrote:
> On Tue, Jun 20, 2017 at 7:41 PM, Hugh Dickins <hughd@google.com> wrote:
> > On Wed, 21 Jun 2017, kernel test robot wrote:
> >
> > Thanks for the report: yes, this is the same one as Dave Jones
> > found yesterday, which is fixed by this patch posted last night:
> 
> .. and that patch is in current -git now, so hopefully we're all good.
> 
> 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.

No, the tree looks good now, thanks.  You're right that Oleg raised a
concern about how mmap(MAP_GROWSDOWN) behaves, and is wondering about
how to make it more sensible: but that's neither a vulnerability nor
a regression - he agreed minor, to think about another time.  He's
also been fielding a concern from the CRIU people, we're hoping that's
just something they need to fix at their end - ah, no, I see Oleg has
just replied ahead of me, not digested yet, I'll look into that later...

Hugh

      parent reply	other threads:[~2017-06-21 19:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21  2:35 kernel test robot
2017-06-21  2:41 ` Hugh Dickins
2017-06-21 18:29   ` Linus Torvalds
2017-06-21 19:33     ` Oleg Nesterov
2017-06-21 19:39       ` Linus Torvalds
2017-06-21 20:27         ` Oleg Nesterov
2017-06-21 20:30           ` Linus Torvalds
2017-06-21 20:56             ` Oleg Nesterov
2017-06-21 22:19               ` Linus Torvalds
2017-06-22  1:07                 ` Hugh Dickins
2017-06-22 10:58                   ` Dmitry Safonov
2017-06-22 15:16                   ` Oleg Nesterov
2017-06-22 18:04                     ` Hugh Dickins
2017-06-22 20:51                       ` Oleg Nesterov
2017-06-22  4:23       ` Hugh Dickins
2017-06-21 19:39     ` Hugh Dickins [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=alpine.LSU.2.11.1706211238180.17033@eggly.anvils \
    --to=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=mhocko@suse.com \
    --cc=oleg@redhat.com \
    --cc=torvalds@linux-foundation.org \
    --cc=w@1wt.eu \
    --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 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®