From: syzbot <syzbot+list2d3cd42628405a68164a@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 (Jul 2025)
Date: Fri, 25 Jul 2025 05:39:30 -0700 [thread overview]
Message-ID: <68837b02.a00a0220.2f88df.004d.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, 5 new issues were detected and 13 were fixed.
In total, 52 issues are still open and 220 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 3934 Yes WARNING in bch2_trans_srcu_unlock
https://syzkaller.appspot.com/bug?extid=1e515cab343dbe5aa38a
<2> 1253 Yes INFO: task hung in bch2_journal_reclaim_thread (2)
https://syzkaller.appspot.com/bug?extid=820dc3b465c69f766a57
<3> 853 Yes kernel BUG in bch2_trans_update_by_path
https://syzkaller.appspot.com/bug?extid=210dfbddd64294066983
<4> 754 Yes kernel BUG in bch2_quota_check_limit
https://syzkaller.appspot.com/bug?extid=8364d1e040a88ed5657d
<5> 459 Yes WARNING in bch2_trans_put
https://syzkaller.appspot.com/bug?extid=291aef749c5cbb9ca2fd
<6> 346 Yes INFO: task hung in bch2_readahead
https://syzkaller.appspot.com/bug?extid=a6060114362257e9798a
<7> 335 Yes WARNING in __bch2_truncate_folio
https://syzkaller.appspot.com/bug?extid=3d11e35eeafe176a6c5b
<8> 158 Yes WARNING in bch2_alloc_sectors_start_trans
https://syzkaller.appspot.com/bug?extid=23573dac1278bb26916d
<9> 124 Yes general protection fault in put_pwq_unlocked (2)
https://syzkaller.appspot.com/bug?extid=aa930d41d2f32904c5da
<10> 62 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-07-25 12:39 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=68837b02.a00a0220.2f88df.004d.GAE@google.com \
--to=syzbot+list2d3cd42628405a68164a@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.