[v6.1] kernel BUG in __gfs2_glock_put (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 50cbba13faa2 Linux 6.1.159
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=145e749a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a5cbd268406bf43
dashboard link: https://syzkaller.appspot.com/bug?extid=54d849f0dc4b7a29275b
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/50ceb00b1b39/disk-50cbba13.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ebb8883b9a29/vmlinux-50cbba13.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7edc2a795f03/bzImage-50cbba13.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+54d849...@syzkaller.appspotmail.com

gfs2: fsid=syz:syz.0: G: s:UN n:2/208e f: t:UN d:EX/0 a:0 v:0 r:-128 m:20 p:1
------------[ cut here ]------------
kernel BUG at fs/gfs2/glock.c:289!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 52 Comm: kworker/1:1H Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Workqueue: glock_workqueue glock_work_func
RIP: 0010:__gfs2_glock_put+0x3d3/0x420 fs/gfs2/glock.c:289
Code: 00 00 e8 70 40 f5 fd 40 84 ed 75 2c e8 06 3e f5 fd e9 e3 fd ff ff e8 fc 3d f5 fd 31 ff 48 89 de ba 01 00 00 00 e8 0d de ff ff <0f> 0b e8 e6 3d f5 fd 0f 0b e9 2c ff ff ff e8 da 3d f5 fd e8 0d df
RSP: 0018:ffffc90000bd7c08 EFLAGS: 00010246
RAX: e928dd67ba9b7d00 RBX: ffff888067d91a68 RCX: ffff88801e285940
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: dffffc0000000000 R09: fffff5200017ae95
R10: fffff5200017ae95 R11: 1ffff9200017ae94 R12: dffffc0000000000
R13: 1ffff1100f0a2015 R14: ffff888078510000 R15: ffff888067d91d58
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f5c8b407000 CR3: 000000007eb13000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
process_one_work+0x898/0x1160 kernel/workqueue.c:2292
worker_thread+0xaa2/0x1250 kernel/workqueue.c:2439
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__gfs2_glock_put+0x3d3/0x420 fs/gfs2/glock.c:289
Code: 00 00 e8 70 40 f5 fd 40 84 ed 75 2c e8 06 3e f5 fd e9 e3 fd ff ff e8 fc 3d f5 fd 31 ff 48 89 de ba 01 00 00 00 e8 0d de ff ff <0f> 0b e8 e6 3d f5 fd 0f 0b e9 2c ff ff ff e8 da 3d f5 fd e8 0d df
RSP: 0018:ffffc90000bd7c08 EFLAGS: 00010246
RAX: e928dd67ba9b7d00 RBX: ffff888067d91a68 RCX: ffff88801e285940
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: dffffc0000000000 R09: fffff5200017ae95
R10: fffff5200017ae95 R11: 1ffff9200017ae94 R12: dffffc0000000000
R13: 1ffff1100f0a2015 R14: ffff888078510000 R15: ffff888067d91d58
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f5c8b407000 CR3: 000000007eb13000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup