From: syzbot <syzbot+listdc301befec0a5cb43b3e@syzkaller.appspotmail.com>
To: kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly bcachefs report (Jun 2025)
Date: Tue, 24 Jun 2025 00:39:27 -0700 [thread overview]
Message-ID: <685a562f.a00a0220.2e5631.005e.GAE@google.com> (raw)
Hello bcachefs maintainers/developers,
This is a 31-day syzbot report for the bcachefs subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/bcachefs
During the period, 15 new issues were detected and 8 were fixed.
In total, 102 issues are still open and 190 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 30829 Yes INFO: task hung in bch2_copygc_stop
https://syzkaller.appspot.com/bug?extid=c6fd966ebbdea1e8ff08
<2> 7874 Yes INFO: task hung in __closure_sync
https://syzkaller.appspot.com/bug?extid=7bf808f7fe4a6549f36e
<3> 3875 Yes WARNING in bch2_trans_srcu_unlock
https://syzkaller.appspot.com/bug?extid=1e515cab343dbe5aa38a
<4> 1497 Yes INFO: task hung in __bch2_fs_stop
https://syzkaller.appspot.com/bug?extid=6d3e28b33490b3085412
<5> 1236 Yes INFO: task hung in bch2_journal_reclaim_thread (2)
https://syzkaller.appspot.com/bug?extid=820dc3b465c69f766a57
<6> 442 Yes WARNING in bch2_trans_put
https://syzkaller.appspot.com/bug?extid=291aef749c5cbb9ca2fd
<7> 361 Yes kernel panic: trans should be locked, unlocked by bch2_btree_update_start
https://syzkaller.appspot.com/bug?extid=d540192e763531d307ff
<8> 343 Yes UBSAN: shift-out-of-bounds in __bch2_btree_node_hash_insert
https://syzkaller.appspot.com/bug?extid=029d1989099aa5ae3e89
<9> 326 Yes WARNING in __bch2_truncate_folio
https://syzkaller.appspot.com/bug?extid=3d11e35eeafe176a6c5b
<10> 324 Yes INFO: task hung in bch2_readahead
https://syzkaller.appspot.com/bug?extid=a6060114362257e9798a
---
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.
next reply other threads:[~2025-06-24 7:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 7:39 syzbot [this message]
2025-06-24 16:36 ` [syzbot] Monthly bcachefs report (Jun 2025) Kent Overstreet
2025-06-24 17:31 ` Alan Huang
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=685a562f.a00a0220.2e5631.005e.GAE@google.com \
--to=syzbot+listdc301befec0a5cb43b3e@syzkaller.appspotmail.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@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