Hello, syzbot found the following issue on: HEAD commit: abf2050f51fd Merge tag 'media/v6.12-1' of git://git.kernel.. git tree: bpf console output: https://syzkaller.appspot.com/x/log.txt?x=100fc99f980000 kernel config: https://syzkaller.appspot.com/x/.config?x=bc30a30374b0753 dashboard link: https://syzkaller.appspot.com/bug?extid=c6c4861455fdd207f160 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14ee7107980000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/367fc75d0a34/disk-abf2050f.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/8df13e2678de/vmlinux-abf2050f.xz kernel image: https://storage.googleapis.com/syzbot-assets/138b13f7dbdb/bzImage-abf2050f.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+c6c4861455fdd207f160@xxxxxxxxxxxxxxxxxxxxxxxxx BUG: MAX_STACK_TRACE_ENTRIES too low! turning off the locking correctness validator. CPU: 0 UID: 0 PID: 16 Comm: ksoftirqd/0 Not tainted 6.11.0-syzkaller-09959-gabf2050f51fd #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 save_trace+0x926/0xb50 kernel/locking/lockdep.c:579 check_prev_add kernel/locking/lockdep.c:3219 [inline] check_prevs_add kernel/locking/lockdep.c:3277 [inline] validate_chain+0x2bde/0x5920 kernel/locking/lockdep.c:3901 __lock_acquire+0x1384/0x2050 kernel/locking/lockdep.c:5199 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5822 __raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline] _raw_spin_lock+0x2e/0x40 kernel/locking/spinlock.c:154 htab_lock_bucket+0x1a4/0x370 kernel/bpf/hashtab.c:167 htab_map_delete_elem+0x1df/0x6b0 kernel/bpf/hashtab.c:1430 bpf_prog_bc20a984d57ef3f1+0x67/0x6b bpf_dispatcher_nop_func include/linux/bpf.h:1257 [inline] __bpf_prog_run include/linux/filter.h:701 [inline] bpf_prog_run include/linux/filter.h:708 [inline] __bpf_trace_run kernel/trace/bpf_trace.c:2318 [inline] bpf_trace_run2+0x2ec/0x540 kernel/trace/bpf_trace.c:2359 __traceiter_kfree+0x2b/0x50 include/trace/events/kmem.h:94 trace_kfree include/trace/events/kmem.h:94 [inline] kfree+0x35e/0x440 mm/slub.c:4715 security_task_free+0xa4/0x1a0 security/security.c:3178 __put_task_struct+0xf9/0x290 kernel/fork.c:977 put_task_struct include/linux/sched/task.h:144 [inline] delayed_put_task_struct+0x125/0x300 kernel/exit.c:228 rcu_do_batch kernel/rcu/tree.c:2567 [inline] rcu_core+0xaaa/0x17a0 kernel/rcu/tree.c:2823 handle_softirqs+0x2c5/0x980 kernel/softirq.c:554 run_ksoftirqd+0xca/0x130 kernel/softirq.c:927 smpboot_thread_fn+0x544/0xa30 kernel/smpboot.c:164 kthread+0x2f0/0x390 kernel/kthread.c:389 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </TASK> --- 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 syzkaller@xxxxxxxxxxxxxxxx. 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 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 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
