From: syzbot <syzbot+list9f3b98537c8cbdd7becc@syzkaller.appspotmail.com>
To: jlbec@evilplan.org, joseph.qi@linux.alibaba.com,
linux-kernel@vger.kernel.org, mark@fasheh.com,
ocfs2-devel@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly ocfs2 report (Oct 2025)
Date: Thu, 02 Oct 2025 23:37:31 -0700 [thread overview]
Message-ID: <68df6f2b.050a0220.2c17c1.001a.GAE@google.com> (raw)
Hello ocfs2 maintainers/developers,
This is a 31-day syzbot report for the ocfs2 subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/ocfs2
During the period, 3 new issues were detected and 0 were fixed.
In total, 68 issues are still open and 22 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 281324 Yes possible deadlock in ocfs2_try_remove_refcount_tree
https://syzkaller.appspot.com/bug?extid=1fed2de07d8e11a3ec1b
<2> 83983 Yes possible deadlock in dqget
https://syzkaller.appspot.com/bug?extid=6e493c165d26d6fcbf72
<3> 59630 Yes possible deadlock in ocfs2_acquire_dquot
https://syzkaller.appspot.com/bug?extid=51244a05705883616c95
<4> 30450 Yes possible deadlock in ocfs2_reserve_suballoc_bits
https://syzkaller.appspot.com/bug?extid=5d516fba7bc3c966c9a9
<5> 19560 Yes possible deadlock in ocfs2_init_acl
https://syzkaller.appspot.com/bug?extid=4007ab5229e732466d9f
<6> 18277 Yes possible deadlock in ocfs2_reserve_local_alloc_bits
https://syzkaller.appspot.com/bug?extid=843fa26882088a9ee7e3
<7> 11625 Yes possible deadlock in ocfs2_setattr
https://syzkaller.appspot.com/bug?extid=d78497256d53041ee229
<8> 4857 No possible deadlock in ocfs2_xattr_set
https://syzkaller.appspot.com/bug?extid=ba9a789bd1f4d21fcefe
<9> 3408 Yes kernel BUG in ocfs2_write_cluster_by_desc
https://syzkaller.appspot.com/bug?extid=18a87160c7d64ba2e2f6
<10> 3185 Yes possible deadlock in ocfs2_lock_global_qf
https://syzkaller.appspot.com/bug?extid=b53d753ae8fb473e2397
---
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-10-03 6:37 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=68df6f2b.050a0220.2c17c1.001a.GAE@google.com \
--to=syzbot+list9f3b98537c8cbdd7becc@syzkaller.appspotmail.com \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--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