From: syzbot <syzbot+list55f13d56985d7df20cbc@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 (Aug 2025)
Date: Tue, 26 Aug 2025 00:13:33 -0700 [thread overview]
Message-ID: <68ad5e9d.050a0220.37038e.00ad.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, 7 new issues were detected and 1 were fixed.
In total, 40 issues are still open and 224 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 4006 Yes WARNING in bch2_trans_srcu_unlock
https://syzkaller.appspot.com/bug?extid=1e515cab343dbe5aa38a
<2> 1442 Yes INFO: task hung in bch2_journal_reclaim_thread (2)
https://syzkaller.appspot.com/bug?extid=820dc3b465c69f766a57
<3> 758 Yes kernel BUG in bch2_quota_check_limit
https://syzkaller.appspot.com/bug?extid=8364d1e040a88ed5657d
<4> 483 Yes WARNING in bch2_trans_put
https://syzkaller.appspot.com/bug?extid=291aef749c5cbb9ca2fd
<5> 369 Yes WARNING in __bch2_truncate_folio
https://syzkaller.appspot.com/bug?extid=3d11e35eeafe176a6c5b
<6> 292 Yes INFO: task hung in bch2_fs_read_only
https://syzkaller.appspot.com/bug?extid=c7aacacf99dcfd3475a7
<7> 241 Yes WARNING in bch2_alloc_sectors_start_trans
https://syzkaller.appspot.com/bug?extid=23573dac1278bb26916d
<8> 125 Yes general protection fault in put_pwq_unlocked (2)
https://syzkaller.appspot.com/bug?extid=aa930d41d2f32904c5da
<9> 120 Yes kernel BUG in __bch2_trans_commit (3)
https://syzkaller.appspot.com/bug?extid=b6ef9edaba01d5b4e43f
<10> 69 Yes KMSAN: uninit-value in LZ4_decompress_safe_partial
https://syzkaller.appspot.com/bug?extid=3c88ea590c13f5f92152
---
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-08-26 7:13 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=68ad5e9d.050a0220.37038e.00ad.GAE@google.com \
--to=syzbot+list55f13d56985d7df20cbc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.