Hello,
syzbot found the following issue on:
HEAD commit: f6e38ae624cf Linux 6.1.158
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=12622012580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=68aa5a3af1cb953a
dashboard link:
https://syzkaller.appspot.com/bug?extid=7bf14de7f5fbcf32d79f
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/c1bd671a9def/disk-f6e38ae6.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/fa0af998ea40/vmlinux-f6e38ae6.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/e5512d873524/Image-f6e38ae6.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+7bf14d...@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: 0 PID: 8264 Comm: gfs2_quotad Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025
Call trace:
dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
__dump_stack+0x30/0x40 lib/dump_stack.c:88
dump_stack_lvl+0xf8/0x160 lib/dump_stack.c:106
dump_stack+0x1c/0x5c lib/dump_stack.c:113
assign_lock_key+0x224/0x258 kernel/locking/lockdep.c:974
register_lock_class+0x1ac/0x694 kernel/locking/lockdep.c:1287
__lock_acquire+0x150/0x6544 kernel/locking/lockdep.c:4928
lock_acquire+0x20c/0x644 kernel/locking/lockdep.c:5662
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
_raw_spin_lock_irqsave+0x6c/0xb4 kernel/locking/spinlock.c:162
finish_wait+0xc8/0x1ac kernel/sched/wait.c:410
gfs2_quotad+0x390/0x4fc fs/gfs2/quota.c:1579
kthread+0x250/0x2d8 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:850
list_del corruption. prev->next should be ffff8000212e7d98, but was 0000000000000000. (prev=ffff0000fdad4bd8)
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:61!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 8264 Comm: gfs2_quotad Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025
pstate: 624000c5 (nZCv daIF +PAN -UAO +TCO -DIT -SSBS BTYPE=--)
pc : __list_del_entry_valid+0x13c/0x158 lib/list_debug.c:59
lr : __list_del_entry_valid+0x13c/0x158 lib/list_debug.c:59
sp : ffff8000212e7c70
x29: ffff8000212e7c70
x28: 0000000000000000
x27: 0000000000000bb8
x26: 0000000000001770 x25: dfff800000000000 x24: dfff800000000000
x23: ffff0000fdad47c0 x22: dfff800000000000 x21: ffff0000fdad4bd8
x20: ffff0000fdad4bd8 x19: ffff8000212e7d98 x18: ffff800011abbcc0
x17: 20747562202c3839 x16: ffff8000082e7de8
x15: 3038666666662065
x14: 6220646c756f6873
x13: 2938646234646164
x12: 0000000000ff0100
x11: ff0080000830a28c x10: 0000000000000000
x9 : 10ba1cd423099c00
x8 : 10ba1cd423099c00
x7 : 74707572726f6320 x6 : ffff800008307460
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff8000082e7efc
x2 : 0000000000000001 x1 : 0000000100000001 x0 : 000000000000006d
Call trace:
__list_del_entry_valid+0x13c/0x158 lib/list_debug.c:59
__list_del_entry include/linux/list.h:134 [inline]
list_del_init include/linux/list.h:206 [inline]
finish_wait+0xd4/0x1ac kernel/sched/wait.c:411
gfs2_quotad+0x390/0x4fc fs/gfs2/quota.c:1579
kthread+0x250/0x2d8 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:850
Code: 91028000 aa1303e1 aa1503e3 95bfbbe3 (d4210000)
---[ end trace 0000000000000000 ]---
---
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