From: syzbot <syzbot+list1844da6a324b378d2182@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 (Mar 2025)
Date: Wed, 19 Mar 2025 14:29:25 -0700 [thread overview]
Message-ID: <67db3735.050a0220.3657bb.0145.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, 17 new issues were detected and 3 were fixed.
In total, 160 issues are still open and 138 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 29679 Yes INFO: task hung in bch2_copygc_stop
https://syzkaller.appspot.com/bug?extid=c6fd966ebbdea1e8ff08
<2> 7346 Yes INFO: task hung in __closure_sync
https://syzkaller.appspot.com/bug?extid=7bf808f7fe4a6549f36e
<3> 5807 Yes KMSAN: uninit-value in bch2_inode_v3_validate
https://syzkaller.appspot.com/bug?extid=3cd97352d16f0e6066d9
<4> 3541 Yes WARNING in bch2_trans_srcu_unlock
https://syzkaller.appspot.com/bug?extid=1e515cab343dbe5aa38a
<5> 3442 Yes KASAN: slab-use-after-free Read in percpu_ref_put (2)
https://syzkaller.appspot.com/bug?extid=905d719acdbd213bf67e
<6> 2491 Yes WARNING in bch2_fs_release
https://syzkaller.appspot.com/bug?extid=08d08d52c3a09bfc70f7
<7> 2333 Yes KMSAN: uninit-value in rw_aux_tree_set (2)
https://syzkaller.appspot.com/bug?extid=ed52fb987e4b52cbfad9
<8> 1166 Yes INFO: task hung in bch2_journal_reclaim_thread (2)
https://syzkaller.appspot.com/bug?extid=820dc3b465c69f766a57
<9> 983 Yes possible deadlock in bch2_symlink
https://syzkaller.appspot.com/bug?extid=7836a68852a10ec3d790
<10> 821 Yes KMSAN: uninit-value in bch2_trans_start_alloc_update
https://syzkaller.appspot.com/bug?extid=f02ee424846cc4e04e04
---
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-03-19 21:29 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=67db3735.050a0220.3657bb.0145.GAE@google.com \
--to=syzbot+list1844da6a324b378d2182@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.