From: syzbot <syzbot+list0717046fea3bd04a43a1@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 (Jun 2026)
Date: Tue, 09 Jun 2026 21:32:26 -0700 [thread overview]
Message-ID: <6a28e8da.39669fcc.33b062.00af.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, 4 new issues were detected and 0 were fixed.
In total, 47 issues are still open and 49 have already been fixed.
There are also 2 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 420199 Yes possible deadlock in ocfs2_try_remove_refcount_tree
https://syzkaller.appspot.com/bug?extid=1fed2de07d8e11a3ec1b
<2> 47417 Yes possible deadlock in ocfs2_reserve_suballoc_bits
https://syzkaller.appspot.com/bug?extid=5d516fba7bc3c966c9a9
<3> 29868 Yes possible deadlock in ocfs2_init_acl
https://syzkaller.appspot.com/bug?extid=4007ab5229e732466d9f
<4> 19085 Yes possible deadlock in ocfs2_setattr
https://syzkaller.appspot.com/bug?extid=d78497256d53041ee229
<5> 14896 Yes kernel BUG in link_path_walk
https://syzkaller.appspot.com/bug?extid=d222f4b7129379c3d5bc
<6> 9171 No possible deadlock in ocfs2_xattr_set
https://syzkaller.appspot.com/bug?extid=ba9a789bd1f4d21fcefe
<7> 6252 Yes kernel BUG in ocfs2_write_cluster_by_desc
https://syzkaller.appspot.com/bug?extid=18a87160c7d64ba2e2f6
<8> 2665 Yes possible deadlock in ocfs2_evict_inode
https://syzkaller.appspot.com/bug?extid=b225d4dfce6219600c42
<9> 448 Yes kernel BUG in ocfs2_reserve_suballoc_bits
https://syzkaller.appspot.com/bug?extid=fd05de09d1267725aa95
<10> 401 Yes kernel BUG in ocfs2_dio_wr_get_block
https://syzkaller.appspot.com/bug?extid=f8b081be889b639423bb
---
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:[~2026-06-10 4:32 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=6a28e8da.39669fcc.33b062.00af.GAE@google.com \
--to=syzbot+list0717046fea3bd04a43a1@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