From: syzbot <syzbot+liste26a67e46fe73e904149@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 2024)
Date: Tue, 11 Jun 2024 01:27:25 -0700 [thread overview]
Message-ID: <0000000000002502d7061a9909cf@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, 37 new issues were detected and 15 were fixed.
In total, 59 issues are still open and 30 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 2800 No WARNING in cleanup_srcu_struct (4)
https://syzkaller.appspot.com/bug?extid=6cf577c8ed4e23fe436b
<2> 1722 Yes WARNING in bch2_trans_srcu_unlock
https://syzkaller.appspot.com/bug?extid=1e515cab343dbe5aa38a
<3> 1620 Yes INFO: task hung in __closure_sync
https://syzkaller.appspot.com/bug?extid=7bf808f7fe4a6549f36e
<4> 1070 Yes KMSAN: uninit-value in bch2_inode_v3_invalid
https://syzkaller.appspot.com/bug?extid=d3803303d5b280e059d8
<5> 578 Yes BUG: MAX_LOCK_DEPTH too low! (4)
https://syzkaller.appspot.com/bug?extid=46405fa9afa07e6c8c40
<6> 221 Yes kernel BUG in gc_bucket
https://syzkaller.appspot.com/bug?extid=246b47da27f8e7e7d6fb
<7> 187 No INFO: task hung in bch2_readahead
https://syzkaller.appspot.com/bug?extid=a6060114362257e9798a
<8> 185 Yes KMSAN: uninit-value in bch2_alloc_v4_invalid
https://syzkaller.appspot.com/bug?extid=3b2968fa4953885dd66a
<9> 148 Yes kernel BUG in bch2_fs_journal_stop
https://syzkaller.appspot.com/bug?extid=10b936c5eaee2819b49b
<10> 104 Yes INFO: task hung in bch2_fs_read_only_work
https://syzkaller.appspot.com/bug?extid=8996d8f176cf946ef641
---
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:[~2024-06-11 8:27 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=0000000000002502d7061a9909cf@google.com \
--to=syzbot+liste26a67e46fe73e904149@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