From: syzbot <syzbot+list88c61bedfe3e28153b24@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 2024)
Date: Tue, 13 Aug 2024 01:53:25 -0700 [thread overview]
Message-ID: <0000000000001a9128061f8cbee7@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 1 were fixed.
In total, 71 issues are still open and 52 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 4330 Yes kernel BUG in bch2_fs_journal_stop
https://syzkaller.appspot.com/bug?extid=10b936c5eaee2819b49b
<2> 2944 Yes INFO: task hung in __closure_sync
https://syzkaller.appspot.com/bug?extid=7bf808f7fe4a6549f36e
<3> 1364 Yes BUG: MAX_LOCK_DEPTH too low! (4)
https://syzkaller.appspot.com/bug?extid=46405fa9afa07e6c8c40
<4> 398 Yes KMSAN: uninit-value in bch2_alloc_v4_invalid
https://syzkaller.appspot.com/bug?extid=3b2968fa4953885dd66a
<5> 246 No INFO: task hung in bch2_readahead
https://syzkaller.appspot.com/bug?extid=a6060114362257e9798a
<6> 221 No WARNING in bch2_trans_put
https://syzkaller.appspot.com/bug?extid=291aef749c5cbb9ca2fd
<7> 215 Yes INFO: task hung in bch2_fs_read_only_work
https://syzkaller.appspot.com/bug?extid=8996d8f176cf946ef641
<8> 138 Yes INFO: task hung in __bch2_fs_stop
https://syzkaller.appspot.com/bug?extid=6d3e28b33490b3085412
<9> 86 Yes possible deadlock in bch2_gc_mark_key
https://syzkaller.appspot.com/bug?extid=050e797ad21ccc3f5d1a
<10> 82 Yes WARNING in __bch2_truncate_folio
https://syzkaller.appspot.com/bug?extid=3d11e35eeafe176a6c5b
---
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-08-13 8:53 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=0000000000001a9128061f8cbee7@google.com \
--to=syzbot+list88c61bedfe3e28153b24@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