All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+693dc11fcb53120b5559@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, bgeffon@google.com,
	 linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	peterx@redhat.com,  rdunlap@infradead.org,
	syzkaller-bugs@googlegroups.com,  torvalds@linux-foundation.org
Subject: Re: BUG: unable to handle kernel paging request in kernel_get_mempolicy
Date: Mon, 06 Apr 2020 22:26:03 -0700	[thread overview]
Message-ID: <000000000000a3afc905a2ac9e77@google.com> (raw)
In-Reply-To: <20200407012702.GB48345@xz-x1>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger crash:

Reported-and-tested-by: syzbot+693dc11fcb53120b5559@syzkaller.appspotmail.com

Tested on:

commit:         23800bff mm/mempolicy: Allow lookup_node() to handle fatal..
git tree:       https://github.com/xzpeter/linux.git
kernel config:  https://syzkaller.appspot.com/x/.config?x=288d637f7bebfd40
dashboard link: https://syzkaller.appspot.com/bug?extid=693dc11fcb53120b5559
compiler:       gcc (GCC) 9.0.0 20181231 (experimental)

Note: testing is done by a robot and is best-effort only.


  reply	other threads:[~2020-04-07  5:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06 18:16 BUG: unable to handle kernel paging request in kernel_get_mempolicy syzbot
2020-04-07  0:47 ` Peter Xu
2020-04-07  1:05   ` Randy Dunlap
2020-04-07  1:05     ` syzbot
2020-04-07  1:06     ` syzbot
2020-04-07  1:27     ` Peter Xu
2020-04-07  5:26       ` syzbot [this message]
2020-04-07  1:39   ` Andrew Morton
2020-04-07  1:55     ` Peter Xu
2020-04-07  2:15       ` Andrew Morton
2020-04-07  2:42         ` Peter Xu
2020-04-07  8:27           ` Dmitry Vyukov
2020-04-07 15:59             ` Peter Xu

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=000000000000a3afc905a2ac9e77@google.com \
    --to=syzbot+693dc11fcb53120b5559@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bgeffon@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=peterx@redhat.com \
    --cc=rdunlap@infradead.org \
    --cc=syzkaller-bugs@googlegroups.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 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.