[v6.6] kernel BUG in gfs2_glock_nq

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6282921b6825 Linux 6.6.94
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1280a182580000
kernel config: https://syzkaller.appspot.com/x/.config?x=96da6b2210cda427
dashboard link: https://syzkaller.appspot.com/bug?extid=e41682c0c00227f58699
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/a3bf0d8e22b2/disk-6282921b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d1d442f782d0/vmlinux-6282921b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a8378f4b7e1b/bzImage-6282921b.xz

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

gfs2: fsid=syz:syz.0: new: gfs2_quota_sync+0x411/0x5a0 fs/gfs2/quota.c:1344
gfs2: fsid=syz:syz.0: pid: 5770
gfs2: fsid=syz:syz.0: lock type: 8 req lock state : 1
gfs2: fsid=syz:syz.0: G: s:EX n:8/1 f:qb t:EX d:EX/0 a:0 v:0 r:5 m:20 p:0
gfs2: fsid=syz:syz.0: H: s:EX f:cH e:0 p:5770 [syz-executor] gfs2_quota_sync+0x411/0x5a0 fs/gfs2/quota.c:1344
------------[ cut here ]------------
kernel BUG at fs/gfs2/glock.c:1589!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 5770 Comm: syz-executor Not tainted 6.6.94-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:add_to_queue fs/gfs2/glock.c:1589 [inline]
RIP: 0010:gfs2_glock_nq+0x113b/0x1420 fs/gfs2/glock.c:1614
Code: 7b 99 3d fe 41 0f b7 0e 48 c7 c7 60 9a ef 8a 4c 89 e6 89 da e8 b6 47 ba 06 31 ff 48 8b 74 24 08 ba 01 00 00 00 e8 35 74 ff ff <0f> 0b 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 45 f1 ff ff 4c 89 f7
RSP: 0018:ffffc900042b79f8 EFLAGS: 00010246
RAX: 561e6d3a6af75300 RBX: 0000000000000008 RCX: ffff88802bee5a00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffff88805ca81fc0 R08: ffffffff8e49ab2f R09: 1ffffffff1c93565
R10: dffffc0000000000 R11: fffffbfff1c93566 R12: ffff88805a685280
R13: ffff88801c370e18 R14: ffff88801c370e5a R15: ffff88801c370e22
FS: 000055556913b500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffe747fdd28 CR3: 00000000625ed000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
gfs2_glock_nq_init fs/gfs2/glock.h:252 [inline]
do_sync+0x3c1/0xe00 fs/gfs2/quota.c:912
gfs2_quota_sync+0x411/0x5a0 fs/gfs2/quota.c:1344
gfs2_sync_fs+0x4c/0xb0 fs/gfs2/super.c:670
sync_filesystem+0xea/0x220 fs/sync.c:56
generic_shutdown_super+0x6f/0x2b0 fs/super.c:666
kill_block_super+0x44/0x90 fs/super.c:1660
deactivate_locked_super+0x97/0x100 fs/super.c:481
cleanup_mnt+0x429/0x4c0 fs/namespace.c:1250
task_work_run+0x1ce/0x250 kernel/task_work.c:239
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f2b9578fc57
Code: a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 a8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffe747fe4d8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007f2b95810925 RCX: 00007f2b9578fc57
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffe747fe590
RBP: 00007ffe747fe590 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffe747ff620
R13: 00007f2b95810925 R14: 00000000000e0246 R15: 00007ffe747ff660
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:add_to_queue fs/gfs2/glock.c:1589 [inline]
RIP: 0010:gfs2_glock_nq+0x113b/0x1420 fs/gfs2/glock.c:1614
Code: 7b 99 3d fe 41 0f b7 0e 48 c7 c7 60 9a ef 8a 4c 89 e6 89 da e8 b6 47 ba 06 31 ff 48 8b 74 24 08 ba 01 00 00 00 e8 35 74 ff ff <0f> 0b 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 45 f1 ff ff 4c 89 f7
RSP: 0018:ffffc900042b79f8 EFLAGS: 00010246
RAX: 561e6d3a6af75300 RBX: 0000000000000008 RCX: ffff88802bee5a00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffff88805ca81fc0 R08: ffffffff8e49ab2f R09: 1ffffffff1c93565
R10: dffffc0000000000 R11: fffffbfff1c93566 R12: ffff88805a685280
R13: ffff88801c370e18 R14: ffff88801c370e5a R15: ffff88801c370e22
FS: 000055556913b500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffe747fdd28 CR3: 00000000625ed000 CR4: 00000000003506f0
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: 6282921b6825 Linux 6.6.94
git tree: linux-6.6.y

console output: https://syzkaller.appspot.com/x/log.txt?x=12c4a182580000

kernel config: https://syzkaller.appspot.com/x/.config?x=96da6b2210cda427
dashboard link: https://syzkaller.appspot.com/bug?extid=e41682c0c00227f58699
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15d97370580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17032b0c580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a3bf0d8e22b2/disk-6282921b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d1d442f782d0/vmlinux-6282921b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a8378f4b7e1b/bzImage-6282921b.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/b547533bd3ec/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=10570b0c580000)

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

gfs2: fsid=syz:syz.0: new: gfs2_quota_sync+0x411/0x5a0 fs/gfs2/quota.c:1344

gfs2: fsid=syz:syz.0: pid: 5769

gfs2: fsid=syz:syz.0: lock type: 8 req lock state : 1
gfs2: fsid=syz:syz.0: G: s:EX n:8/1 f:qb t:EX d:EX/0 a:0 v:0 r:5 m:20 p:0

gfs2: fsid=syz:syz.0: H: s:EX f:cH e:0 p:5769 [syz-executor159] gfs2_quota_sync+0x411/0x5a0 fs/gfs2/quota.c:1344

------------[ cut here ]------------
kernel BUG at fs/gfs2/glock.c:1589!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN

CPU: 0 PID: 5769 Comm: syz-executor159 Not tainted 6.6.94-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:add_to_queue fs/gfs2/glock.c:1589 [inline]
RIP: 0010:gfs2_glock_nq+0x113b/0x1420 fs/gfs2/glock.c:1614
Code: 7b 99 3d fe 41 0f b7 0e 48 c7 c7 60 9a ef 8a 4c 89 e6 89 da e8 b6 47 ba 06 31 ff 48 8b 74 24 08 ba 01 00 00 00 e8 35 74 ff ff <0f> 0b 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 45 f1 ff ff 4c 89 f7

RSP: 0018:ffffc90004457898 EFLAGS: 00010246
RAX: 5fa62e04681d8700 RBX: 0000000000000008 RCX: ffff888026375a00

RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000

RBP: ffff8880770b3be0 R08: ffffffff8e49ab2f R09: 1ffffffff1c93565
R10: dffffc0000000000 R11: fffffbfff1c93566 R12: ffff88802ea99280
R13: ffff88802e2cd818 R14: ffff88802e2cd85a R15: ffff88802e2cd822
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000

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

CR2: 000055c9b744d010 CR3: 0000000019289000 CR4: 00000000003506f0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
gfs2_glock_nq_init fs/gfs2/glock.h:252 [inline]
do_sync+0x3c1/0xe00 fs/gfs2/quota.c:912
gfs2_quota_sync+0x411/0x5a0 fs/gfs2/quota.c:1344
gfs2_sync_fs+0x4c/0xb0 fs/gfs2/super.c:670
sync_filesystem+0xea/0x220 fs/sync.c:56
generic_shutdown_super+0x6f/0x2b0 fs/super.c:666
kill_block_super+0x44/0x90 fs/super.c:1660
deactivate_locked_super+0x97/0x100 fs/super.c:481
cleanup_mnt+0x429/0x4c0 fs/namespace.c:1250
task_work_run+0x1ce/0x250 kernel/task_work.c:239

exit_task_work include/linux/task_work.h:43 [inline]
do_exit+0x903/0x23c0 kernel/exit.c:874
do_group_exit+0x21b/0x2d0 kernel/exit.c:1023
__do_sys_exit_group kernel/exit.c:1034 [inline]
__se_sys_exit_group kernel/exit.c:1032 [inline]
__x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1032
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f45d832ab09
Code: Unable to access opcode bytes at 0x7f45d832aadf.
RSP: 002b:00007fff759330a8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f45d832ab09
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 00007f45d83b92b0 R08: ffffffffffffffb8 R09: 00000000000125eb
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f45d83b92b0
R13: 0000000000000000 R14: 00007f45d83ba020 R15: 00007f45d82f9050

</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:add_to_queue fs/gfs2/glock.c:1589 [inline]
RIP: 0010:gfs2_glock_nq+0x113b/0x1420 fs/gfs2/glock.c:1614
Code: 7b 99 3d fe 41 0f b7 0e 48 c7 c7 60 9a ef 8a 4c 89 e6 89 da e8 b6 47 ba 06 31 ff 48 8b 74 24 08 ba 01 00 00 00 e8 35 74 ff ff <0f> 0b 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 45 f1 ff ff 4c 89 f7

RSP: 0018:ffffc90004457898 EFLAGS: 00010246
RAX: 5fa62e04681d8700 RBX: 0000000000000008 RCX: ffff888026375a00

RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000

RBP: ffff8880770b3be0 R08: ffffffff8e49ab2f R09: 1ffffffff1c93565
R10: dffffc0000000000 R11: fffffbfff1c93566 R12: ffff88802ea99280
R13: ffff88802e2cd818 R14: ffff88802e2cd85a R15: ffff88802e2cd822
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000

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

CR2: 000055c9b744d010 CR3: 0000000019289000 CR4: 00000000003506f0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---

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.

[syzbot]

syzbot suspects this issue could be fixed by backporting the following commit:

commit ae9f3bd8259a0a8f67be2420e66bb05fbb95af48
git tree: upstream
Author: Andreas Gruenbacher <agru...@redhat.com>
Date: Sat Apr 5 22:31:37 2025 +0000

gfs2: replace sd_aspace with sd_inode

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=160c90f0580000

kernel config: https://syzkaller.appspot.com/x/.config?x=96da6b2210cda427
dashboard link: https://syzkaller.appspot.com/bug?extid=e41682c0c00227f58699

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15d97370580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17032b0c580000

Please keep in mind that other backports might be required as well.

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

[syzbot]

For archival purposes, forwarding an incoming command email to
syzkaller...@googlegroups.com.

***

Subject: kernel BUG in gfs2_glock_nq
Author: sumanth...@yahoo.com

#syz test