From: syzbot <syzbot+list792ff7e60f79eeaa9303@syzkaller.appspotmail.com>
To: gfs2@lists.linux.dev, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly gfs2 report (May 2026)
Date: Sat, 23 May 2026 05:32:43 -0700 [thread overview]
Message-ID: <6a119e6b.170a0220.35b2b7.000a.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, 0 new issues were detected and 0 were fixed.
In total, 33 issues are still open and 44 have already been fixed.
There are also 3 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 413 Yes KASAN: stack-out-of-bounds Read in gfs2_dump_glock
https://syzkaller.appspot.com/bug?extid=7efd59a5a532c57037e6
<2> 72 Yes INFO: task hung in gfs2_recover_journal (4)
https://syzkaller.appspot.com/bug?extid=9013411dc43f3582823a
<3> 49 Yes WARNING in gfs2_ri_update (2)
https://syzkaller.appspot.com/bug?extid=7567dc5c8aa8f68bde74
<4> 2174 Yes INFO: task hung in __gfs2_lookup
https://syzkaller.appspot.com/bug?extid=8a86bdd8c524e46ff97a
<5> 1455 Yes kernel BUG in gfs2_glock_nq (2)
https://syzkaller.appspot.com/bug?extid=70f4e455dee59ab40c80
<6> 92 Yes kernel BUG in qd_put (3)
https://syzkaller.appspot.com/bug?extid=0423714c06c369318794
<7> 91 Yes kernel BUG in gfs2_quota_cleanup (3)
https://syzkaller.appspot.com/bug?extid=af4d53576692f8956fd6
<8> 28 No general protection fault in gfs2_glock_dq (2)
https://syzkaller.appspot.com/bug?extid=5a5f492ccae698fd7434
<9> 14 No kernel BUG in gfs2_trans_add_revoke
https://syzkaller.appspot.com/bug?extid=b17a83b050e9617376f0
<10> 12 Yes KASAN: slab-use-after-free Read in lru_add (2)
https://syzkaller.appspot.com/bug?extid=8921d5debffa05b33b27
---
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-05-23 12: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=6a119e6b.170a0220.35b2b7.000a.GAE@google.com \
--to=syzbot+list792ff7e60f79eeaa9303@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox