From: syzbot <syzbot+c27475eb921c46bbdc62@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, hch@lst.de, jack@suse.com,
jack@suse.cz, linkinjeon@gmail.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, syzkaller-bugs@googlegroups.com,
willy@infradead.org
Subject: Re: [syzbot] [udf?] BUG: unable to handle kernel NULL pointer dereference in __writepage
Date: Thu, 19 Jan 2023 08:31:22 -0800 [thread overview]
Message-ID: <0000000000009cfc1705f2a07641@google.com> (raw)
In-Reply-To: <0000000000003198a505f0076823@google.com>
syzbot has bisected this issue to:
commit 36273e5b4e3a934c6d346c8f0b16b97e018094af
Author: Christoph Hellwig <hch@lst.de>
Date: Sun Nov 13 16:29:02 2022 +0000
udf: remove ->writepage
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15176e66480000
start commit: 77856d911a8c Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=17176e66480000
console output: https://syzkaller.appspot.com/x/log.txt?x=13176e66480000
kernel config: https://syzkaller.appspot.com/x/.config?x=55043d38f21f0e0f
dashboard link: https://syzkaller.appspot.com/bug?extid=c27475eb921c46bbdc62
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=141da6e7880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17d81b8b880000
Reported-by: syzbot+c27475eb921c46bbdc62@syzkaller.appspotmail.com
Fixes: 36273e5b4e3a ("udf: remove ->writepage")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-01-19 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 15:04 syzbot
2023-01-19 16:31 ` syzbot [this message]
2023-01-23 7:36 ` Christoph Hellwig
2023-01-23 17:18 ` Jan Kara
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=0000000000009cfc1705f2a07641@google.com \
--to=syzbot+c27475eb921c46bbdc62@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linkinjeon@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox