From: syzbot <syzbot+listce982f98d810f528a2ee@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 (Jul 2026)
Date: Sat, 04 Jul 2026 05:32:29 -0700 [thread overview]
Message-ID: <6a48fd5d.34acba0d.1e07b.000a.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, 3 new issues were detected and 2 were fixed.
In total, 24 issues are still open and 118 have already been fixed.
There are also 13 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 66 No possible deadlock in btrfs_dirty_inode (2)
https://syzkaller.appspot.com/bug?extid=415a049af48761105c01
<2> 47 No possible deadlock in btrfs_quota_enable (2)
https://syzkaller.appspot.com/bug?extid=3a88c590edd72179657c
<3> 43 Yes WARNING in btrfs_destroy_inode (3)
https://syzkaller.appspot.com/bug?extid=25df068cd8509f8c0fe1
<4> 8 Yes WARNING in can_finish_ordered_extent
https://syzkaller.appspot.com/bug?extid=085adc3f91549d11066a
<5> 6652 Yes kernel BUG in close_ctree
https://syzkaller.appspot.com/bug?extid=2665d678fffcc4608e18
<6> 890 Yes WARNING in btrfs_chunk_alloc
https://syzkaller.appspot.com/bug?extid=e8e56d5d31d38b5b47e7
<7> 484 Yes WARNING in btrfs_remove_chunk
https://syzkaller.appspot.com/bug?extid=e8582cc16881ec70a430
<8> 53 Yes INFO: rcu detected stall in sys_readlink (5)
https://syzkaller.appspot.com/bug?extid=23e14ec82f3c8692eaa9
<9> 32 Yes WARNING in btrfs_free_reserved_data_space_noquota (3)
https://syzkaller.appspot.com/bug?extid=9064acebb06685edb243
<10> 31 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-07-04 12:32 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=6a48fd5d.34acba0d.1e07b.000a.GAE@google.com \
--to=syzbot+listce982f98d810f528a2ee@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