[v6.1] INFO: trying to register non-static key in gfs2_quotad

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 02b72ccb5f9d Linux 6.1.138
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15d9e2f4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=40498c8aeab367b8
dashboard link: https://syzkaller.appspot.com/bug?extid=b62dddd0c7822c0837c4
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/741917d96f57/disk-02b72ccb.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b5e0c69249ae/vmlinux-02b72ccb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/06bfb546fb37/bzImage-02b72ccb.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b62ddd...@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: 5682 Comm: gfs2_quotad Not tainted 6.1.138-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x22e lib/dump_stack.c:106
assign_lock_key+0x1f5/0x230 kernel/locking/lockdep.c:974
register_lock_class+0x20e/0x860 kernel/locking/lockdep.c:1287
__lock_acquire+0x160/0x7c50 kernel/locking/lockdep.c:4928
lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662
__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+0xb8/0x1d0 kernel/sched/wait.c:410
gfs2_quotad+0x4e6/0x670 fs/gfs2/quota.c:1579
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
list_del corruption. prev->next should be ffffc90003497e58, but was 0000000000000000. (prev=ffff8880264ccbd8)
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:61!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 5682 Comm: gfs2_quotad Not tainted 6.1.138-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
RIP: 0010:__list_del_entry_valid+0x10a/0x120 lib/list_debug.c:59
Code: e8 8b 47 f8 05 0f 0b 48 c7 c7 e0 11 bf 8a 48 89 de e8 7a 47 f8 05 0f 0b 48 c7 c7 40 12 bf 8a 48 89 de 4c 89 f9 e8 66 47 f8 05 <0f> 0b 48 c7 c7 c0 12 bf 8a 48 89 de 4c 89 f1 e8 52 47 f8 05 0f 0b
RSP: 0018:ffffc90003497d30 EFLAGS: 00010046
RAX: 000000000000006d RBX: ffffc90003497e58 RCX: b0805e9a3272b200
RDX: 0000000000000000 RSI: 0000000080000001 RDI: 0000000000000000
RBP: dffffc0000000000 R08: dffffc0000000000 R09: ffffed10171e4f34
R10: ffffed10171e4f34 R11: 1ffff110171e4f33 R12: dffffc0000000000
R13: ffff8880264ccb98 R14: ffff8880264ccbd8 R15: ffff8880264ccbd8
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000005000 CR3: 000000007cb1e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__list_del_entry include/linux/list.h:134 [inline]
list_del_init include/linux/list.h:206 [inline]
finish_wait+0xc3/0x1d0 kernel/sched/wait.c:411
gfs2_quotad+0x4e6/0x670 fs/gfs2/quota.c:1579
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:__list_del_entry_valid+0x10a/0x120 lib/list_debug.c:59
Code: e8 8b 47 f8 05 0f 0b 48 c7 c7 e0 11 bf 8a 48 89 de e8 7a 47 f8 05 0f 0b 48 c7 c7 40 12 bf 8a 48 89 de 4c 89 f9 e8 66 47 f8 05 <0f> 0b 48 c7 c7 c0 12 bf 8a 48 89 de 4c 89 f1 e8 52 47 f8 05 0f 0b
RSP: 0018:ffffc90003497d30 EFLAGS: 00010046
RAX: 000000000000006d RBX: ffffc90003497e58 RCX: b0805e9a3272b200
RDX: 0000000000000000 RSI: 0000000080000001 RDI: 0000000000000000
RBP: dffffc0000000000 R08: dffffc0000000000 R09: ffffed10171e4f34
R10: ffffed10171e4f34 R11: 1ffff110171e4f33 R12: dffffc0000000000
R13: ffff8880264ccb98 R14: ffff8880264ccbd8 R15: ffff8880264ccbd8
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000005000 CR3: 000000007cb1e000 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

[syzbot]

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