From: syzbot <syzbot+0b9cadf5fc45a98a5083@syzkaller.appspotmail.com>
To: chao@kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
timmurray@google.com
Subject: Re: [syzbot] possible deadlock in f2fs_write_checkpoint
Date: Wed, 02 Feb 2022 18:23:07 -0800 [thread overview]
Message-ID: <0000000000009303f605d713d014@google.com> (raw)
In-Reply-To: <0000000000004cede805d58728c3@google.com>
syzbot has bisected this issue to:
commit e4544b63a7ee49e7fbebf35ece0a6acd3b9617ae
Author: Tim Murray <timmurray@google.com>
Date: Fri Jan 7 20:48:44 2022 +0000
f2fs: move f2fs to use reader-unfair rwsems
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=108e6078700000
start commit: 6abab1b81b65 Add linux-next specific files for 20220202
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=128e6078700000
console output: https://syzkaller.appspot.com/x/log.txt?x=148e6078700000
kernel config: https://syzkaller.appspot.com/x/.config?x=b8d8750556896349
dashboard link: https://syzkaller.appspot.com/bug?extid=0b9cadf5fc45a98a5083
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12de9cb8700000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11953798700000
Reported-by: syzbot+0b9cadf5fc45a98a5083@syzkaller.appspotmail.com
Fixes: e4544b63a7ee ("f2fs: move f2fs to use reader-unfair rwsems")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2022-02-03 2:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 9:09 [syzbot] possible deadlock in f2fs_write_checkpoint syzbot
2022-02-02 13:34 ` syzbot
2022-02-03 2:23 ` 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=0000000000009303f605d713d014@google.com \
--to=syzbot+0b9cadf5fc45a98a5083@syzkaller.appspotmail.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=timmurray@google.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