From: syzbot <syzbot+list1912688380c32552e820@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly btrfs report (Mar 2026)
Date: Tue, 03 Mar 2026 00:06:28 -0800 [thread overview]
Message-ID: <69a69684.050a0220.21ae90.0006.GAE@google.com> (raw)
Hello btrfs maintainers/developers,
This is a 31-day syzbot report for the btrfs subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/btrfs
During the period, 1 new issues were detected and 0 were fixed.
In total, 42 issues are still open and 112 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 5569 Yes WARNING in btrfs_space_info_update_bytes_may_use
https://syzkaller.appspot.com/bug?extid=8edfa01e46fd9fe3fbfb
<2> 1340 Yes WARNING in btrfs_create_pending_block_groups (2)
https://syzkaller.appspot.com/bug?extid=b0643a1387dac0572b27
<3> 1226 Yes WARNING in btrfs_commit_transaction (2)
https://syzkaller.appspot.com/bug?extid=dafbca0e20fbc5946925
<4> 727 Yes WARNING in btrfs_chunk_alloc
https://syzkaller.appspot.com/bug?extid=e8e56d5d31d38b5b47e7
<5> 505 Yes WARNING in cleanup_transaction
https://syzkaller.appspot.com/bug?extid=021d10c4d4edc87daa03
<6> 443 Yes WARNING in btrfs_remove_chunk
https://syzkaller.appspot.com/bug?extid=e8582cc16881ec70a430
<7> 206 Yes WARNING in __btrfs_free_extent (3)
https://syzkaller.appspot.com/bug?extid=480676efc0c3a76b5214
<8> 183 Yes kernel BUG in clear_state_bit
https://syzkaller.appspot.com/bug?extid=78dbea1c214b5413bdd3
<9> 77 Yes WARNING in btrfs_run_delayed_refs (2)
https://syzkaller.appspot.com/bug?extid=810ea5febd3b79bdd384
<10> 55 Yes INFO: task hung in __alloc_workqueue (2)
https://syzkaller.appspot.com/bug?extid=ead9101689c4ca30dbe8
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
To disable reminders for individual bugs, reply with the following command:
#syz set <Ref> no-reminders
To change bug's subsystems, reply with:
#syz set <Ref> subsystems: new-subsystem
You may send multiple commands in a single email message.
reply other threads:[~2026-03-03 8:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=69a69684.050a0220.21ae90.0006.GAE@google.com \
--to=syzbot+list1912688380c32552e820@syzkaller.appspotmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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