From: syzbot <syzbot+035a381ea1afb63f098d@syzkaller.appspotmail.com>
To: changfengnan@vivo.com, chao@kernel.org, frank.li@vivo.com,
jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
wuhoipok@gmail.com
Subject: Re: [f2fs-dev] [syzbot] BUG: unable to handle kernel NULL pointer dereference in f2fs_stop_discard_thread
Date: Thu, 27 Oct 2022 20:34:21 -0700 [thread overview]
Message-ID: <000000000000f79f5905ec0fee38@google.com> (raw)
In-Reply-To: <000000000000a7077705eae5f90c@google.com>
syzbot has bisected this issue to:
commit 4d67490498acb4ffcef5ba7bc44990d46e66a44c
Author: Fengnan Chang <changfengnan@vivo.com>
Date: Thu Aug 19 08:02:37 2021 +0000
f2fs: Don't create discard thread when device doesn't support realtime discard
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17da7522880000
start commit: 247f34f7b803 Linux 6.1-rc2
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=143a7522880000
console output: https://syzkaller.appspot.com/x/log.txt?x=103a7522880000
kernel config: https://syzkaller.appspot.com/x/.config?x=a66c6c673fb555e8
dashboard link: https://syzkaller.appspot.com/bug?extid=035a381ea1afb63f098d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11d92d6a880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12e5dbba880000
Reported-by: syzbot+035a381ea1afb63f098d@syzkaller.appspotmail.com
Fixes: 4d67490498ac ("f2fs: Don't create discard thread when device doesn't support realtime discard")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2022-10-28 3:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 8:05 [f2fs-dev] [syzbot] BUG: unable to handle kernel NULL pointer dereference in f2fs_stop_discard_thread syzbot
2022-10-28 3:34 ` syzbot [this message]
2022-10-28 3:49 ` Chao Yu
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=000000000000f79f5905ec0fee38@google.com \
--to=syzbot+035a381ea1afb63f098d@syzkaller.appspotmail.com \
--cc=changfengnan@vivo.com \
--cc=chao@kernel.org \
--cc=frank.li@vivo.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wuhoipok@gmail.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;
as well as URLs for NNTP newsgroup(s).