[v6.1] kernel BUG in __gfs2_glock_put

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7e69c33e4858 Linux 6.1.142
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=147d3770580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c13e5b1e791632f6
dashboard link: https://syzkaller.appspot.com/bug?extid=8d0ca86132fa82d878c2
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/66227cc7a961/disk-7e69c33e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/800396fbefa3/vmlinux-7e69c33e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9164f62e8709/bzImage-7e69c33e.xz

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

gfs2: fsid=syz:syz.0: G: s:UN n:2/819 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: 1077 Comm: kworker/1:1H Not tainted 6.1.142-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Workqueue: glock_workqueue glock_work_func
RIP: 0010:__gfs2_glock_put+0x3d3/0x420 fs/gfs2/glock.c:289
Code: 00 00 e8 60 8b f4 fd 40 84 ed 75 2c e8 f6 88 f4 fd e9 e3 fd ff ff e8 ec 88 f4 fd 31 ff 48 89 de ba 01 00 00 00 e8 0d de ff ff <0f> 0b e8 d6 88 f4 fd 0f 0b e9 2c ff ff ff e8 ca 88 f4 fd e8 fd 31
RSP: 0000:ffffc9000504fc08 EFLAGS: 00010246
RAX: d3a36dc342fe9800 RBX: ffff8880777f6a40 RCX: ffff888026443b80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: dffffc0000000000 R09: fffff52000a09e95
R10: fffff52000a09e95 R11: 1ffff92000a09e94 R12: dffffc0000000000
R13: 1ffff1100f2c4815 R14: ffff888079624000 R15: ffff8880777f6d30
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd753549850 CR3: 000000002ef0b000 CR4: 00000000003526e0
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 60 8b f4 fd 40 84 ed 75 2c e8 f6 88 f4 fd e9 e3 fd ff ff e8 ec 88 f4 fd 31 ff 48 89 de ba 01 00 00 00 e8 0d de ff ff <0f> 0b e8 d6 88 f4 fd 0f 0b e9 2c ff ff ff e8 ca 88 f4 fd e8 fd 31
RSP: 0000:ffffc9000504fc08 EFLAGS: 00010246
RAX: d3a36dc342fe9800 RBX: ffff8880777f6a40 RCX: ffff888026443b80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: dffffc0000000000 R09: fffff52000a09e95
R10: fffff52000a09e95 R11: 1ffff92000a09e94 R12: dffffc0000000000
R13: 1ffff1100f2c4815 R14: ffff888079624000 R15: ffff8880777f6d30
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f61b1583338 CR3: 0000000063c93000 CR4: 00000000003526e0
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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3f5b4c104b7d Linux 6.6.95
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12df9ebc580000
kernel config: https://syzkaller.appspot.com/x/.config?x=747dbf84b0ecd30c
dashboard link: https://syzkaller.appspot.com/bug?extid=7a0b805bd932cb2b7b02
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

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

Downloadable assets:

disk image: https://storage.googleapis.com/syzbot-assets/421f6e2d0cd1/disk-3f5b4c10.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/90250695b20b/vmlinux-3f5b4c10.xz
kernel image: https://storage.googleapis.com/syzbot-assets/32250e77bce9/bzImage-3f5b4c10.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:

Reported-by: syzbot+7a0b80...@syzkaller.appspotmail.com

gfs2: fsid=syz:syz.0: G: s:UN n:2/819 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:302!

invalid opcode: 0000 [#1] PREEMPT SMP KASAN

CPU: 1 PID: 54 Comm: kworker/1:1H Not tainted 6.6.95-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Workqueue: glock_workqueue glock_work_func

RIP: 0010:__gfs2_glock_put+0x355/0x3b0 fs/gfs2/glock.c:302
Code: 8b 3f 48 89 de e8 db 15 ff ff eb 25 e8 54 50 e5 fd e9 d1 fe ff ff e8 4a 50 e5 fd 31 ff 48 89 de ba 01 00 00 00 e8 bb df ff ff <0f> 0b e8 34 50 e5 fd 31 f6 65 ff 0d d3 73 63 7c 40 0f 94 c5 40 0f
RSP: 0000:ffffc90000bf7b88 EFLAGS: 00010246
RAX: b56c938a073e1e00 RBX: ffff888030fda4f8 RCX: ffff888018699e00

RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000

RBP: 0000000000000000 R08: ffffc90000bf7427 R09: 1ffff9200017ee84
R10: dffffc0000000000 R11: fffff5200017ee85 R12: dffffc0000000000
R13: 1ffff1100f220015 R14: ffff888079100000 R15: ffff888030fda7e8

FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00007f89660e2000 CR3: 0000000062fdd000 CR4: 00000000003506e0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>

process_one_work kernel/workqueue.c:2634 [inline]
process_scheduled_works+0xa45/0x15b0 kernel/workqueue.c:2711
worker_thread+0xa55/0xfc0 kernel/workqueue.c:2792
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293

</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---

RIP: 0010:__gfs2_glock_put+0x355/0x3b0 fs/gfs2/glock.c:302
Code: 8b 3f 48 89 de e8 db 15 ff ff eb 25 e8 54 50 e5 fd e9 d1 fe ff ff e8 4a 50 e5 fd 31 ff 48 89 de ba 01 00 00 00 e8 bb df ff ff <0f> 0b e8 34 50 e5 fd 31 f6 65 ff 0d d3 73 63 7c 40 0f 94 c5 40 0f
RSP: 0000:ffffc90000bf7b88 EFLAGS: 00010246
RAX: b56c938a073e1e00 RBX: ffff888030fda4f8 RCX: ffff888018699e00

RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000

RBP: 0000000000000000 R08: ffffc90000bf7427 R09: 1ffff9200017ee84
R10: dffffc0000000000 R11: fffff5200017ee85 R12: dffffc0000000000
R13: 1ffff1100f220015 R14: ffff888079100000 R15: ffff888030fda7e8

FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00007f89660e2000 CR3: 0000000062fdd000 CR4: 00000000003506e0

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.

[syzbot]