Hello,
syzbot found the following issue on:
HEAD commit: ca1c9012c941 Linux 6.1.26
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=1293ead8280000
kernel config:
https://syzkaller.appspot.com/x/.config?x=f95cba4715d63af9
dashboard link:
https://syzkaller.appspot.com/bug?extid=8e8da32faf31462f2486
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
syz repro:
https://syzkaller.appspot.com/x/repro.syz?x=10d76808280000
C reproducer:
https://syzkaller.appspot.com/x/repro.c?x=13a5a2b4280000
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/b6b74e769ec1/disk-ca1c9012.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/31fce9ce6f18/vmlinux-ca1c9012.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/cd73b5bb5ef4/Image-ca1c9012.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+8e8da3...@syzkaller.appspotmail.com
------------[ cut here ]------------
lockdep bfs error:-1
WARNING: CPU: 1 PID: 3893 at kernel/locking/lockdep.c:2067 print_bfs_bug+0x34/0x48 kernel/locking/lockdep.c:2067
Modules linked in:
CPU: 1 PID: 3893 Comm: dhcpcd Not tainted 6.1.26-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
pstate: 604000c5 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : print_bfs_bug+0x34/0x48 kernel/locking/lockdep.c:2067
lr : print_bfs_bug+0x34/0x48 kernel/locking/lockdep.c:2067
sp : ffff800020426cc0
x29: ffff800020426cc0 x28: 0000000000000003 x27: ffff0000c7920a58
x26: 00000000000003dd x25: ffff800019192e18 x24: ffff8000183c6000
x23: 1fffe00018f2414b x22: 0000000000000013 x21: ffff800019192da8
x20: 0000000000000001 x19: 00000000ffffffff x18: ffff800020426e40
x17: 0000000000000000 x16: ffff8000120e0c54 x15: 0000000000000000
x14: 0000000000000000 x13: 0000000000000001 x12: 0000000000000001
x11: ff808000081ae818 x10: 0000000000000000 x9 : 3691702cd3d42000
x8 : 3691702cd3d42000 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff8000204265b8 x4 : ffff800015672960 x3 : ffff800008585158
x2 : 0000000000000001 x1 : 0000000000000003 x0 : 0000000000000000
Call trace:
print_bfs_bug+0x34/0x48 kernel/locking/lockdep.c:2067
check_irq_usage kernel/locking/lockdep.c:2792 [inline]
check_prev_add kernel/locking/lockdep.c:3102 [inline]
check_prevs_add kernel/locking/lockdep.c:3217 [inline]
validate_chain kernel/locking/lockdep.c:3832 [inline]
__lock_acquire+0x618c/0x764c kernel/locking/lockdep.c:5056
lock_acquire+0x26c/0x7cc kernel/locking/lockdep.c:5669
__raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
_raw_spin_lock+0x54/0x6c kernel/locking/spinlock.c:154
update_cfs_rq_load_avg kernel/sched/fair.c:4026 [inline]
update_load_avg+0x194/0x1278 kernel/sched/fair.c:4185
put_prev_entity+0x228/0x400 kernel/sched/fair.c:5082
pick_next_task_fair+0x3bc/0x944 kernel/sched/fair.c:7814
__pick_next_task kernel/sched/core.c:5864 [inline]
pick_next_task kernel/sched/core.c:6373 [inline]
__schedule+0x61c/0x1c98 kernel/sched/core.c:6518
preempt_schedule_common+0xf4/0x1e8 kernel/sched/core.c:6723
preempt_schedule+0x64/0x84 kernel/sched/core.c:6747
__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:152 [inline]
_raw_spin_unlock_irqrestore+0xa8/0xac kernel/locking/spinlock.c:194
__debug_check_no_obj_freed lib/debugobjects.c:1006 [inline]
debug_check_no_obj_freed+0x4f0/0x50c lib/debugobjects.c:1027
free_pages_prepare mm/page_alloc.c:1466 [inline]
free_pcp_prepare mm/page_alloc.c:1510 [inline]
free_unref_page_prepare+0x450/0x1070 mm/page_alloc.c:3388
free_unref_page+0x80/0x444 mm/page_alloc.c:3484
free_the_page mm/page_alloc.c:770 [inline]
__free_pages+0x1a0/0x1cc mm/page_alloc.c:5648
__free_slab+0x110/0x29c mm/slub.c:2016
free_slab mm/slub.c:2031 [inline]
discard_slab+0x5c/0xdc mm/slub.c:2037
__unfreeze_partials+0x158/0x198 mm/slub.c:2586
put_cpu_partial+0x18c/0x1fc mm/slub.c:2662
__slab_free+0x1a0/0x26c mm/slub.c:3538
do_slab_free mm/slub.c:3615 [inline]
___cache_free+0x164/0x198 mm/slub.c:3668
qlink_free+0x5c/0xac mm/kasan/quarantine.c:168
qlist_free_all+0x40/0xcc mm/kasan/quarantine.c:187
kasan_quarantine_reduce+0x124/0x130 mm/kasan/quarantine.c:294
__kasan_slab_alloc+0x2c/0x8c mm/kasan/common.c:305
kasan_slab_alloc include/linux/kasan.h:201 [inline]
slab_post_alloc_hook+0x74/0x458 mm/slab.h:737
slab_alloc_node mm/slub.c:3398 [inline]
slab_alloc mm/slub.c:3406 [inline]
__kmem_cache_alloc_lru mm/slub.c:3413 [inline]
kmem_cache_alloc+0x230/0x37c mm/slub.c:3422
mt_alloc_one lib/maple_tree.c:152 [inline]
mas_alloc_nodes+0x228/0x704 lib/maple_tree.c:1277
mas_node_count_gfp lib/maple_tree.c:1359 [inline]
mas_preallocate+0x124/0x2dc lib/maple_tree.c:5806
do_brk_flags+0x6c4/0xa60 mm/mmap.c:2994
__do_sys_brk mm/mmap.c:262 [inline]
__se_sys_brk mm/mmap.c:170 [inline]
__arm64_sys_brk+0x778/0x884 mm/mmap.c:170
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581
irq event stamp: 20187338
hardirqs last enabled at (20187337): [<ffff8000120ded20>] __exit_to_kernel_mode arch/arm64/kernel/entry-common.c:84 [inline]
hardirqs last enabled at (20187337): [<ffff8000120ded20>] exit_to_kernel_mode+0xe8/0x118 arch/arm64/kernel/entry-common.c:94
hardirqs last disabled at (20187338): [<ffff8000121abf3c>] __schedule+0x2a4/0x1c98 kernel/sched/core.c:6453
softirqs last enabled at (20187336): [<ffff800008020d74>] softirq_handle_end kernel/softirq.c:414 [inline]
softirqs last enabled at (20187336): [<ffff800008020d74>] __do_softirq+0xc14/0xea0 kernel/softirq.c:600
softirqs last disabled at (20187327): [<ffff80000802a948>] ____do_softirq+0x14/0x20 arch/arm64/kernel/irq.c:79
---[ 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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
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.
If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup