From: syzbot <syzbot+list5daa17ef4218bd47bbac@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly btrfs report (Apr 2025)
Date: Wed, 23 Apr 2025 00:50:39 -0700 [thread overview]
Message-ID: <68089bcf.050a0220.36a438.000b.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 1 were fixed.
In total, 46 issues are still open and 98 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 6543 Yes kernel BUG in close_ctree
https://syzkaller.appspot.com/bug?extid=2665d678fffcc4608e18
<2> 4030 Yes WARNING in btrfs_space_info_update_bytes_may_use
https://syzkaller.appspot.com/bug?extid=8edfa01e46fd9fe3fbfb
<3> 1190 Yes BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low! (7)
https://syzkaller.appspot.com/bug?extid=74f79df25c37437e4d5a
<4> 651 Yes INFO: task hung in evict (2)
https://syzkaller.appspot.com/bug?extid=65b1e2d8f2d618a93e96
<5> 639 Yes WARNING in btrfs_commit_transaction (2)
https://syzkaller.appspot.com/bug?extid=dafbca0e20fbc5946925
<6> 560 Yes WARNING in btrfs_create_pending_block_groups (2)
https://syzkaller.appspot.com/bug?extid=b0643a1387dac0572b27
<7> 397 Yes WARNING in btrfs_chunk_alloc
https://syzkaller.appspot.com/bug?extid=e8e56d5d31d38b5b47e7
<8> 386 Yes general protection fault in btrfs_root_node
https://syzkaller.appspot.com/bug?extid=9c3e0cdfbfe351b0bc0e
<9> 336 Yes WARNING in cleanup_transaction
https://syzkaller.appspot.com/bug?extid=021d10c4d4edc87daa03
<10> 288 Yes WARNING in btrfs_remove_chunk
https://syzkaller.appspot.com/bug?extid=e8582cc16881ec70a430
---
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:[~2025-04-23 7:50 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=68089bcf.050a0220.36a438.000b.GAE@google.com \
--to=syzbot+list5daa17ef4218bd47bbac@syzkaller.appspotmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.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