From: syzbot <syzbot+list2e82c29d724b61416433@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 (Jun 2026)
Date: Tue, 02 Jun 2026 21:32:22 -0700 [thread overview]
Message-ID: <6a1fae56.3b158e77.2846f8.084b.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 0 were fixed.
In total, 23 issues are still open and 114 have already been fixed.
There are also 11 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 185 Yes WARNING in btrfs_run_delayed_refs (2)
https://syzkaller.appspot.com/bug?extid=810ea5febd3b79bdd384
<2> 63 No possible deadlock in btrfs_dirty_inode (2)
https://syzkaller.appspot.com/bug?extid=415a049af48761105c01
<3> 37 Yes WARNING in btrfs_destroy_inode (3)
https://syzkaller.appspot.com/bug?extid=25df068cd8509f8c0fe1
<4> 7 Yes INFO: task hung in btrfs_invalidate_folio (4)
https://syzkaller.appspot.com/bug?extid=c7443384724bb0f9e913
<5> 2 No KASAN: slab-use-after-free Write in btrfs_put_root
https://syzkaller.appspot.com/bug?extid=b3d472d13f9d7bf20669
<6> 6592 Yes kernel BUG in close_ctree
https://syzkaller.appspot.com/bug?extid=2665d678fffcc4608e18
<7> 847 Yes WARNING in btrfs_chunk_alloc
https://syzkaller.appspot.com/bug?extid=e8e56d5d31d38b5b47e7
<8> 460 Yes WARNING in btrfs_remove_chunk
https://syzkaller.appspot.com/bug?extid=e8582cc16881ec70a430
<9> 31 Yes WARNING in btrfs_free_reserved_data_space_noquota (3)
https://syzkaller.appspot.com/bug?extid=9064acebb06685edb243
<10> 29 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-06-03 4: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=6a1fae56.3b158e77.2846f8.084b.GAE@google.com \
--to=syzbot+list2e82c29d724b61416433@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