[syzbot] [gfs2?] kernel BUG in do_xmote

[syzbot <syzbot+353de08f32ce69361b89@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    52ba76324a9d Add linux-next specific files for 20251013
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=159e25e2580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=99cb6b007a8889ef
dashboard link: https://syzkaller.appspot.com/bug?extid=353de08f32ce69361b89
compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1589f304580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1492bb34580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1729256319ee/disk-52ba7632.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a3152cfcba7c/vmlinux-52ba7632.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4065a3b3d959/bzImage-52ba7632.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/85dc141e7c83/mount_0.gz
  fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=10dc5542580000)

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

gfs2: fsid=syz:syz.0: G:  s:EX n:3/2090 f:lyfaqo t:EX d:EX/0 a:0 v:0 r:3 m:20 p:0
gfs2: fsid=syz:syz.0:  H: s:EX f:nW e:0 p:6072 [syz.0.21] alloc_dinode+0x16a/0x550 fs/gfs2/inode.c:414
gfs2: fsid=syz:syz.0:  R: n:8336 f:80000000 b:826/826 i:7 q:0 r:0 e:7811
------------[ cut here ]------------
kernel BUG at fs/gfs2/glock.c:674!
Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
CPU: 0 UID: 0 PID: 6064 Comm: kworker/0:2H Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Workqueue: gfs2-glock/syz:syz glock_work_func
RIP: 0010:do_xmote+0x706/0x750 fs/gfs2/glock.c:674
Code: 38 c1 0f 8c a9 fe ff ff 48 89 df e8 64 77 29 fe e9 9c fe ff ff e8 ea cd c3 fd 31 ff 48 89 de ba 01 00 00 00 e8 1b e9 fe ff 90 <0f> 0b e8 d3 cd c3 fd 31 ff 48 89 de ba 01 00 00 00 e8 04 e9 fe ff
RSP: 0018:ffffc90002ff79a0 EFLAGS: 00010246
RAX: 89b42d9b8aee9500 RBX: ffff8880406efb60 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 00000000ffffffff
RBP: ffffffff8bb183c0 R08: ffff888075ab0bab R09: 1ffff1100eb56175
R10: dffffc0000000000 R11: ffffed100eb56176 R12: dffffc0000000000
R13: 0000000000000001 R14: 0000000000000001 R15: 0000000000000015
FS:  0000000000000000(0000) GS:ffff888125d08000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f742dc70f98 CR3: 000000007b84a000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 glock_work_func+0x2a8/0x580 fs/gfs2/glock.c:1002
 process_one_work kernel/workqueue.c:3263 [inline]
 process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3346
 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3427
 kthread+0x711/0x8a0 kernel/kthread.c:463
 ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:do_xmote+0x706/0x750 fs/gfs2/glock.c:674
Code: 38 c1 0f 8c a9 fe ff ff 48 89 df e8 64 77 29 fe e9 9c fe ff ff e8 ea cd c3 fd 31 ff 48 89 de ba 01 00 00 00 e8 1b e9 fe ff 90 <0f> 0b e8 d3 cd c3 fd 31 ff 48 89 de ba 01 00 00 00 e8 04 e9 fe ff
RSP: 0018:ffffc90002ff79a0 EFLAGS: 00010246
RAX: 89b42d9b8aee9500 RBX: ffff8880406efb60 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 00000000ffffffff
RBP: ffffffff8bb183c0 R08: ffff888075ab0bab R09: 1ffff1100eb56175
R10: dffffc0000000000 R11: ffffed100eb56176 R12: dffffc0000000000
R13: 0000000000000001 R14: 0000000000000001 R15: 0000000000000015
FS:  0000000000000000(0000) GS:ffff888125d08000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f742dc70f98 CR3: 000000007b84a000 CR4: 00000000003526f0


---
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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

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