From: syzbot <syzbot+list62f8684d17ebec83082d@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 2024)
Date: Thu, 24 Oct 2024 01:02:23 -0700 [thread overview]
Message-ID: <6719ff0f.050a0220.1e4b4d.00a1.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, 18 new issues were detected and 3 were fixed.
In total, 51 issues are still open and 6 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 29174 Yes possible deadlock in ocfs2_try_remove_refcount_tree
https://syzkaller.appspot.com/bug?extid=1fed2de07d8e11a3ec1b
<2> 4466 Yes possible deadlock in dqget
https://syzkaller.appspot.com/bug?extid=6e493c165d26d6fcbf72
<3> 3721 No possible deadlock in ocfs2_acquire_dquot
https://syzkaller.appspot.com/bug?extid=51244a05705883616c95
<4> 2419 Yes possible deadlock in ocfs2_reserve_suballoc_bits
https://syzkaller.appspot.com/bug?extid=5d516fba7bc3c966c9a9
<5> 2175 Yes possible deadlock in ocfs2_reserve_local_alloc_bits
https://syzkaller.appspot.com/bug?extid=843fa26882088a9ee7e3
<6> 1681 Yes possible deadlock in ocfs2_init_acl
https://syzkaller.appspot.com/bug?extid=4007ab5229e732466d9f
<7> 962 Yes general protection fault in ocfs2_prepare_dir_for_insert
https://syzkaller.appspot.com/bug?extid=5a64828fcc4c2ad9b04f
<8> 488 No possible deadlock in ocfs2_xattr_set
https://syzkaller.appspot.com/bug?extid=ba9a789bd1f4d21fcefe
<9> 72 Yes kernel BUG in ocfs2_iget
https://syzkaller.appspot.com/bug?extid=5bdd4953bc58c8fbd6eb
<10> 62 Yes INFO: trying to register non-static key in ocfs2_dlm_shutdown
https://syzkaller.appspot.com/bug?extid=d7935821694d430624ea
---
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-10-24 8:02 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=6719ff0f.050a0220.1e4b4d.00a1.GAE@google.com \
--to=syzbot+list62f8684d17ebec83082d@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 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.