[syzbot] [gfs2?] kernel BUG in __gfs2_glock_put (2)

[syzbot <syzbot+ef4ad020dc976d178975@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    bc6e0ba6c9ba Add linux-next specific files for 20250613
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15cd6e82580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=2f7a2e4d17ed458f
dashboard link: https://syzkaller.appspot.com/bug?extid=ef4ad020dc976d178975
compiler:       Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2430bb0465cc/disk-bc6e0ba6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/436a39deef0a/vmlinux-bc6e0ba6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e314ca5b1eb3/bzImage-bc6e0ba6.xz

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

gfs2: fsid=syz:syz.0: G:  s:UN n:2/925 f:a t:UN d:EX/0 a:0 v:0 r:-128 m:20 p:1
------------[ cut here ]------------
kernel BUG at fs/gfs2/glock.c:274!
Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
CPU: 0 UID: 0 PID: 55 Comm: kworker/0:1H Not tainted 6.16.0-rc1-next-20250613-syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Workqueue: gfs2-glock/syz:syz glock_work_func
RIP: 0010:__gfs2_glock_put+0x384/0x3e0 fs/gfs2/glock.c:274
Code: 3f 48 89 de e8 ed 0e ff ff eb 26 e8 c6 43 cf fd e9 30 fe ff ff e8 bc 43 cf fd 31 ff 48 89 de ba 01 00 00 00 e8 9d de ff ff 90 <0f> 0b e8 a5 43 cf fd 31 f6 65 ff 0d 3c cc ac 0e 40 0f 94 c5 40 0f
RSP: 0018:ffffc9000130fa48 EFLAGS: 00010246
RAX: c5b932becee92b00 RBX: ffff8880572f5fb0 RCX: ffff88801b770000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffc9000130f307 R09: 1ffff92000261e60
R10: dffffc0000000000 R11: fffff52000261e61 R12: dffffc0000000000
R13: 1ffff1100a9dc815 R14: ffff888054ee4000 R15: ffff8880572f62a0
FS:  0000000000000000(0000) GS:ffff888125c41000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005555656fb5c8 CR3: 000000007604a000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 process_one_work kernel/workqueue.c:3235 [inline]
 process_scheduled_works+0xade/0x17b0 kernel/workqueue.c:3318
 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3399
 kthread+0x711/0x8a0 kernel/kthread.c:464
 ret_from_fork+0x3f9/0x770 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__gfs2_glock_put+0x384/0x3e0 fs/gfs2/glock.c:274
Code: 3f 48 89 de e8 ed 0e ff ff eb 26 e8 c6 43 cf fd e9 30 fe ff ff e8 bc 43 cf fd 31 ff 48 89 de ba 01 00 00 00 e8 9d de ff ff 90 <0f> 0b e8 a5 43 cf fd 31 f6 65 ff 0d 3c cc ac 0e 40 0f 94 c5 40 0f
RSP: 0018:ffffc9000130fa48 EFLAGS: 00010246
RAX: c5b932becee92b00 RBX: ffff8880572f5fb0 RCX: ffff88801b770000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffc9000130f307 R09: 1ffff92000261e60
R10: dffffc0000000000 R11: fffff52000261e61 R12: dffffc0000000000
R13: 1ffff1100a9dc815 R14: ffff888054ee4000 R15: ffff8880572f62a0
FS:  0000000000000000(0000) GS:ffff888125c41000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005555656fb5c8 CR3: 000000007604a000 CR4: 00000000003526f0
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 syzkaller@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