From: David Sterba <dsterba@suse.cz>
To: syzbot <syzbot+2c45a55710ac9b888efc@syzkaller.appspotmail.com>
Cc: clm@fb.com, dsterba@suse.com, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] WARNING: suspicious RCU usage in btrfs_dev_stat_inc_and_print
Date: Tue, 3 Mar 2026 17:18:43 +0100 [thread overview]
Message-ID: <20260303161843.GD8455@twin.jikos.cz> (raw)
In-Reply-To: <69a5f980.a70a0220.b118c.0004.GAE@google.com>
On Mon, Mar 02, 2026 at 12:56:32PM -0800, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 7d6661873f6b Add linux-next specific files for 20260226
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1753c202580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=98a1e192f758c1c1
> dashboard link: https://syzkaller.appspot.com/bug?extid=2c45a55710ac9b888efc
> compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
>
> Unfortunately, I don't have any reproducer for this issue yet.
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/4cd2824adb8a/disk-7d666187.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/bbdd4a130d86/vmlinux-7d666187.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/6e3bea3e96f8/bzImage-7d666187.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+2c45a55710ac9b888efc@syzkaller.appspotmail.com
>
> loop0: detected capacity change from 32768 to 0
> =============================
> WARNING: suspicious RCU usage
> syzkaller #0 Not tainted
> -----------------------------
> fs/btrfs/volumes.h:872 suspicious rcu_dereference_check() usage!
#syz invalid
Marking as invalid so it does not appear in the list of issues but
otherwise it's a valid report caused by patch that has been removed.
https://lore.kernel.org/linux-btrfs/20260205114546.210418-1-dsterba@suse.com/
prev parent reply other threads:[~2026-03-03 16:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 20:56 [syzbot] [btrfs?] WARNING: suspicious RCU usage in btrfs_dev_stat_inc_and_print syzbot
2026-03-03 16:18 ` David Sterba [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=20260303161843.GD8455@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+2c45a55710ac9b888efc@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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