[v5.15] INFO: trying to register non-static key in gfs2_quotad

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ac56c046adf4 Linux 5.15.195
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12937de2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e1bb6d24ef2164eb
dashboard link: https://syzkaller.appspot.com/bug?extid=a1fb87899927e521b3ae
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c11ec9487150/disk-ac56c046.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f1130a72d3a0/vmlinux-ac56c046.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7608cb6a3be5/bzImage-ac56c046.xz

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

INFO: trying to register non-static key.
The code is fine but needs lockdep annotation, or maybe
you didn't initialize this object before use?
turning off the locking correctness validator.
CPU: 1 PID: 6360 Comm: gfs2_quotad Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
assign_lock_key+0x1e0/0x1f0 kernel/locking/lockdep.c:937
register_lock_class+0x20e/0x880 kernel/locking/lockdep.c:1250
__lock_acquire+0x160/0x7c60 kernel/locking/lockdep.c:4891
lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0xa4/0xf0 kernel/locking/spinlock.c:162
finish_wait+0xb5/0x1d0 kernel/sched/wait.c:407
gfs2_quotad+0x703/0x880 fs/gfs2/quota.c:1605
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
list_del corruption. prev->next should be ffffc90003b7fe58, but was 0000000000000000
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:61!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 6360 Comm: gfs2_quotad Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:__list_del_entry_valid+0x107/0x120 lib/list_debug.c:59
Code: 48 89 de e8 7b c3 bf 05 0f 0b 48 c7 c7 c0 ac 59 8a 48 89 de e8 6a c3 bf 05 0f 0b 48 c7 c7 20 ad 59 8a 48 89 de e8 59 c3 bf 05 <0f> 0b 48 c7 c7 80 ad 59 8a 48 89 de e8 48 c3 bf 05 0f 0b 00 00 cc
RSP: 0000:ffffc90003b7fd10 EFLAGS: 00010046
RAX: 0000000000000054 RBX: ffffc90003b7fe58 RCX: fa5852e03c93df00
RDX: 0000000000000000 RSI: 0000000080000001 RDI: 0000000000000000
RBP: dffffc0000000000 R08: dffffc0000000000 R09: ffffed1017224f2c
R10: ffffed1017224f2c R11: 1ffff11017224f2b R12: dffffc0000000000
R13: ffff8880191a0b98 R14: ffff8880191a0bd8 R15: ffff8880191a0bd8
FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f59cf8bc840 CR3: 000000006358e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__list_del_entry include/linux/list.h:132 [inline]
list_del_init include/linux/list.h:204 [inline]
finish_wait+0xc0/0x1d0 kernel/sched/wait.c:408
gfs2_quotad+0x703/0x880 fs/gfs2/quota.c:1605
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Modules linked in:
---[ end trace 6a9bbf3c2caa2afd ]---
RIP: 0010:__list_del_entry_valid+0x107/0x120 lib/list_debug.c:59
Code: 48 89 de e8 7b c3 bf 05 0f 0b 48 c7 c7 c0 ac 59 8a 48 89 de e8 6a c3 bf 05 0f 0b 48 c7 c7 20 ad 59 8a 48 89 de e8 59 c3 bf 05 <0f> 0b 48 c7 c7 80 ad 59 8a 48 89 de e8 48 c3 bf 05 0f 0b 00 00 cc
RSP: 0000:ffffc90003b7fd10 EFLAGS: 00010046
RAX: 0000000000000054 RBX: ffffc90003b7fe58 RCX: fa5852e03c93df00
RDX: 0000000000000000 RSI: 0000000080000001 RDI: 0000000000000000
RBP: dffffc0000000000 R08: dffffc0000000000 R09: ffffed1017224f2c
R10: ffffed1017224f2c R11: 1ffff11017224f2b R12: dffffc0000000000
R13: ffff8880191a0b98 R14: ffff8880191a0bd8 R15: ffff8880191a0bd8
FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f59cf8bc840 CR3: 000000006358e000 CR4: 00000000003506e0
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