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

[syzbot]

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+ef4ad0...@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 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]

syzbot has found a reproducer for the following issue on:

HEAD commit: c9cfc122f037 Merge tag 'for-6.18-rc4-tag' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1721a17c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=929790bc044e87d7
dashboard link: https://syzkaller.appspot.com/bug?extid=ef4ad020dc976d178975
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=11c42084580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11df2114580000

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-c9cfc122.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c3f2cad59d49/vmlinux-c9cfc122.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a4cfb61ba836/bzImage-c9cfc122.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/3d8068067f45/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=104bc012580000)

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

loop0: rw=12288, sector=18446744073709551608, nr_sectors = 8 limit=32768
gfs2: fsid=syz:syz.s: Error -5 locking journal for spectator mount.
gfs2: fsid=syz:syz.s: G: s:UN n:2/ffffffffffffffff f:an 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 NOPTI
CPU: 0 UID: 0 PID: 5494 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014

RIP: 0010:__gfs2_glock_put+0x384/0x3e0 fs/gfs2/glock.c:274

Code: 3f 48 89 de e8 7d 0f ff ff eb 26 e8 b6 38 c3 fd e9 30 fe ff ff e8 ac 38 c3 fd 31 ff 48 89 de ba 01 00 00 00 e8 2d df ff ff 90 <0f> 0b e8 95 38 c3 fd 31 f6 65 ff 0d 8c 02 72 0e 40 0f 94 c5 40 0f
RSP: 0018:ffffc90002a6f408 EFLAGS: 00010246
RAX: 29c52adf4a6b3d00 RBX: ffff88801131cfd8 RCX: ffff8880002c0000

RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000

RBP: 0000000000000000 R08: ffffc90002a6ecc7 R09: 1ffff9200054dd98
R10: dffffc0000000000 R11: fffff5200054dd99 R12: dffffc0000000000
R13: 1ffff11007cab015 R14: ffff88803e558000 R15: ffff88801131d2c8
FS: 0000555578b1a500(0000) GS:ffff88808d732000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 000055f461a63048 CR3: 00000000126a6000 CR4: 0000000000352ef0
Call Trace:
<TASK>
gfs2_glock_put_eventually fs/gfs2/super.c:1183 [inline]
gfs2_evict_inode+0xae7/0x1000 fs/gfs2/super.c:1458
evict+0x504/0x9c0 fs/inode.c:810
gfs2_jindex_free+0x39c/0x440 fs/gfs2/super.c:79
init_journal+0x8f1/0x2260 fs/gfs2/ops_fstype.c:833
init_inodes+0xdb/0x320 fs/gfs2/ops_fstype.c:851
gfs2_fill_super+0x1923/0x20d0 fs/gfs2/ops_fstype.c:1255
get_tree_bdev_flags+0x40e/0x4d0 fs/super.c:1691
gfs2_get_tree+0x51/0x1e0 fs/gfs2/ops_fstype.c:1337
vfs_get_tree+0x92/0x2b0 fs/super.c:1751
fc_mount fs/namespace.c:1208 [inline]
do_new_mount_fc fs/namespace.c:3651 [inline]
do_new_mount+0x302/0xa10 fs/namespace.c:3727
do_mount fs/namespace.c:4050 [inline]
__do_sys_mount fs/namespace.c:4238 [inline]
__se_sys_mount+0x313/0x410 fs/namespace.c:4215
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f9033190e6a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffc08e3a548 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffc08e3a5d0 RCX: 00007f9033190e6a
RDX: 0000200000000400 RSI: 0000200000012500 RDI: 00007ffc08e3a590
RBP: 0000200000000400 R08: 00007ffc08e3a5d0 R09: 0000000000804444
R10: 0000000000804444 R11: 0000000000000246 R12: 0000200000012500
R13: 00007ffc08e3a590 R14: 0000000000012636 R15: 00002000000004c0

</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 7d 0f ff ff eb 26 e8 b6 38 c3 fd e9 30 fe ff ff e8 ac 38 c3 fd 31 ff 48 89 de ba 01 00 00 00 e8 2d df ff ff 90 <0f> 0b e8 95 38 c3 fd 31 f6 65 ff 0d 8c 02 72 0e 40 0f 94 c5 40 0f
RSP: 0018:ffffc90002a6f408 EFLAGS: 00010246
RAX: 29c52adf4a6b3d00 RBX: ffff88801131cfd8 RCX: ffff8880002c0000

RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000

RBP: 0000000000000000 R08: ffffc90002a6ecc7 R09: 1ffff9200054dd98
R10: dffffc0000000000 R11: fffff5200054dd99 R12: dffffc0000000000
R13: 1ffff11007cab015 R14: ffff88803e558000 R15: ffff88801131d2c8
FS: 0000555578b1a500(0000) GS:ffff88808d732000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00007fd59ca21eb8 CR3: 00000000126a6000 CR4: 0000000000352ef0


---
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.