From: syzbot <syzbot+20d7e439f76bbbd863a7@syzkaller.appspotmail.com>
To: brauner@kernel.org, chao@kernel.org, frank.li@vivo.com,
jack@suse.cz, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [f2fs?] WARNING in rcu_sync_dtor
Date: Fri, 26 Jul 2024 08:23:02 -0700 [thread overview]
Message-ID: <0000000000004ff2dc061e281637@google.com> (raw)
In-Reply-To: <000000000000b90a8e061e21d12f@google.com>
syzbot has bisected this issue to:
commit b62e71be2110d8b52bf5faf3c3ed7ca1a0c113a5
Author: Chao Yu <chao@kernel.org>
Date: Sun Apr 23 15:49:15 2023 +0000
f2fs: support errors=remount-ro|continue|panic mountoption
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=119745f1980000
start commit: 1722389b0d86 Merge tag 'net-6.11-rc1' of git://git.kernel...
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=139745f1980000
console output: https://syzkaller.appspot.com/x/log.txt?x=159745f1980000
kernel config: https://syzkaller.appspot.com/x/.config?x=b698a1b2fcd7ef5f
dashboard link: https://syzkaller.appspot.com/bug?extid=20d7e439f76bbbd863a7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1237a1f1980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=115edac9980000
Reported-by: syzbot+20d7e439f76bbbd863a7@syzkaller.appspotmail.com
Fixes: b62e71be2110 ("f2fs: support errors=remount-ro|continue|panic mountoption")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-07-26 15:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 7:54 [syzbot] [f2fs?] WARNING in rcu_sync_dtor syzbot
2024-07-26 15:23 ` syzbot [this message]
2024-07-29 9:10 ` Christian Brauner
2024-07-29 13:27 ` Jan Kara
2024-07-29 13:58 ` Theodore Ts'o
2024-07-30 12:38 ` Jan Kara
2024-08-01 22:28 ` Dave Chinner
2024-09-11 1:48 ` Chao Yu
2024-09-11 2:12 ` syzbot
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=0000000000004ff2dc061e281637@google.com \
--to=syzbot+20d7e439f76bbbd863a7@syzkaller.appspotmail.com \
--cc=brauner@kernel.org \
--cc=chao@kernel.org \
--cc=frank.li@vivo.com \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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).