From: syzbot <syzbot+liste224054b66e11f54d148@syzkaller.appspotmail.com>
To: dsterba@suse.com, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly btrfs report (Nov 2026)
Date: Fri, 06 Nov 2026 04:33:48 -0800 [thread overview]
Message-ID: <6aedc92c.a716b02e.a4a62.0001.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, 2 new issues were detected and 1 were fixed.
In total, 31 issues are still open and 121 have already been fixed.
There are also 14 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 213 Yes WARNING in btrfs_run_delayed_refs (2)
https://syzkaller.appspot.com/bug?extid=810ea5febd3b79bdd384
<2> 113 Yes INFO: task hung in __alloc_workqueue (2)
https://syzkaller.appspot.com/bug?extid=ead9101689c4ca30dbe8
<3> 63 No possible deadlock in kernfs_add_one
https://syzkaller.appspot.com/bug?extid=f50d605480fdec503770
<4> 19 No WARNING in __btrfs_update_delayed_inode (4)
https://syzkaller.appspot.com/bug?extid=768687d6d7c96a124e24
<5> 17 Yes WARNING in __add_block_group_free_space
https://syzkaller.appspot.com/bug?extid=6931616d57696102d8aa
<6> 17 Yes WARNING in btrfs_add_to_free_space_tree (2)
https://syzkaller.appspot.com/bug?extid=554a2e08e4abc56984a9
<7> 7 No kernel BUG in set_state_bits (2)
https://syzkaller.appspot.com/bug?extid=64579ad11e26758151bc
<8> 1463 Yes WARNING in btrfs_chunk_alloc
https://syzkaller.appspot.com/bug?extid=e8e56d5d31d38b5b47e7
<9> 696 Yes WARNING in btrfs_remove_chunk
https://syzkaller.appspot.com/bug?extid=e8582cc16881ec70a430
<10> 79 Yes WARNING in btrfs_finish_one_ordered
https://syzkaller.appspot.com/bug?extid=6e54e639e7b934d64304
---
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-11-06 12:33 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=6aedc92c.a716b02e.a4a62.0001.GAE@google.com \
--to=syzbot+liste224054b66e11f54d148@syzkaller.appspotmail.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
all inboxes | Powered by JetHome®