All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+f9238a0a31f9b5603fef@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, linux-fsdevel@vger.kernel.org,
	 linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
	seanjc@google.com,  syzkaller-bugs@googlegroups.com,
	usama.anjum@collabora.com
Subject: Re: [syzbot] [fs?] BUG: unable to handle kernel NULL pointer dereference in do_pagemap_scan
Date: Wed, 07 Aug 2024 22:20:03 -0700	[thread overview]
Message-ID: <000000000000dc521a061f252d4c@google.com> (raw)
In-Reply-To: <000000000000f52642060d4e3750@google.com>

syzbot suspects this issue was fixed by commit:

commit 4cccb6221cae6d020270606b9e52b1678fc8b71a
Author: Muhammad Usama Anjum <usama.anjum@collabora.com>
Date:   Tue Jan 9 11:24:42 2024 +0000

    fs/proc/task_mmu: move mmu notification mechanism inside mm lock

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=141753f9980000
start commit:   fbafc3e621c3 Merge tag 'for_linus' of git://git.kernel.org..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=298e57794135adf0
dashboard link: https://syzkaller.appspot.com/bug?extid=f9238a0a31f9b5603fef
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1108a595e80000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16777bbee80000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: fs/proc/task_mmu: move mmu notification mechanism inside mm lock

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2024-08-08  5:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-25  4:44 [syzbot] [fs?] BUG: unable to handle kernel NULL pointer dereference in do_pagemap_scan syzbot
2024-01-05  1:23 ` Lizhi Xu
2024-01-05  2:04   ` syzbot
2024-08-08  5:20 ` syzbot [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=000000000000dc521a061f252d4c@google.com \
    --to=syzbot+f9238a0a31f9b5603fef@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizhi.xu@windriver.com \
    --cc=seanjc@google.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=usama.anjum@collabora.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.