From: syzbot <syzbot+list2e7521569c2378f26147@syzkaller.appspotmail.com>
To: gfs2@lists.linux.dev, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly gfs2 report (Apr 2026)
Date: Wed, 22 Apr 2026 02:08:34 -0700 [thread overview]
Message-ID: <69e89012.a00a0220.17a17.0028.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 0 were fixed.
In total, 43 issues are still open and 44 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 2097 Yes INFO: task hung in __gfs2_lookup
https://syzkaller.appspot.com/bug?extid=8a86bdd8c524e46ff97a
<2> 1453 Yes kernel BUG in gfs2_glock_nq (2)
https://syzkaller.appspot.com/bug?extid=70f4e455dee59ab40c80
<3> 1398 Yes kernel BUG in gfs2_jindex_free (2)
https://syzkaller.appspot.com/bug?extid=150563285f78ac3e9bd4
<4> 682 Yes WARNING in vfs_setxattr (3)
https://syzkaller.appspot.com/bug?extid=5ce48a14916462cec450
<5> 412 Yes KASAN: stack-out-of-bounds Read in gfs2_dump_glock
https://syzkaller.appspot.com/bug?extid=7efd59a5a532c57037e6
<6> 229 Yes WARNING in chown_common
https://syzkaller.appspot.com/bug?extid=04c2672c56fbb9401640
<7> 155 Yes INFO: task hung in block_invalidate_folio (2)
https://syzkaller.appspot.com/bug?extid=85194ada5aabdfff265b
<8> 139 Yes general protection fault in __gfs2_trans_begin
https://syzkaller.appspot.com/bug?extid=a3a4e5eee651210c6887
<9> 89 Yes kernel BUG in qd_put (3)
https://syzkaller.appspot.com/bug?extid=0423714c06c369318794
<10> 78 Yes kernel BUG in gfs2_quota_cleanup (3)
https://syzkaller.appspot.com/bug?extid=af4d53576692f8956fd6
---
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-04-22 9:08 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=69e89012.a00a0220.17a17.0028.GAE@google.com \
--to=syzbot+list2e7521569c2378f26147@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