From: syzbot <syzbot+list34ab25ce4f800e605e47@syzkaller.appspotmail.com>
To: gfs2@lists.linux.dev, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly gfs2 report (Jun 2025)
Date: Fri, 13 Jun 2025 05:25:34 -0700 [thread overview]
Message-ID: <684c18be.a00a0220.279073.000c.GAE@google.com> (raw)
Hello gfs2 maintainers/developers,
This is a 31-day syzbot report for the gfs2 subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/gfs2
During the period, 4 new issues were detected and 1 were fixed.
In total, 18 issues are still open and 37 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 2244 Yes kernel BUG in gfs2_withdraw
https://syzkaller.appspot.com/bug?extid=ed42f17ebcb58526788c
<2> 1385 Yes kernel BUG in gfs2_glock_nq (2)
https://syzkaller.appspot.com/bug?extid=70f4e455dee59ab40c80
<3> 235 Yes INFO: task hung in __gfs2_lookup
https://syzkaller.appspot.com/bug?extid=8a86bdd8c524e46ff97a
<4> 30 Yes WARNING in gfs2_ri_update (2)
https://syzkaller.appspot.com/bug?extid=7567dc5c8aa8f68bde74
<5> 29 Yes INFO: task hung in gfs2_glock_nq
https://syzkaller.appspot.com/bug?extid=dbb72d38131e90dc1f66
<6> 18 No WARNING in gfs2_put_super
https://syzkaller.appspot.com/bug?extid=56182be23469e01affbc
<7> 8 Yes kernel BUG in qd_put (3)
https://syzkaller.appspot.com/bug?extid=0423714c06c369318794
<8> 6 Yes stack segment fault in gfs2_glock_dq
https://syzkaller.appspot.com/bug?extid=e0dbe53de58ffe4a5f31
<9> 5 No kernel BUG in do_qc
https://syzkaller.appspot.com/bug?extid=bad65435361712796381
<10> 3 No KASAN: slab-use-after-free Write in gfs2_qd_dealloc (3)
https://syzkaller.appspot.com/bug?extid=42a37bf8045847d8f9d2
---
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-06-13 12:25 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=684c18be.a00a0220.279073.000c.GAE@google.com \
--to=syzbot+list34ab25ce4f800e605e47@syzkaller.appspotmail.com \
--cc=gfs2@lists.linux.dev \
--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.