====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.3.39/4404 is trying to acquire lock: ffff888062531238 (&trie->lock){....}-{2:2}, at: trie_delete_elem+0x90/0x710 kernel/bpf/lpm_trie.c:467 but task is already holding lock: ffff8880b902a258 (hrtimer_bases.lock){-.-.}-{2:2}, at: lock_hrtimer_base kernel/time/hrtimer.c:168 [inline] ffff8880b902a258 (hrtimer_bases.lock){-.-.}-{2:2}, at: hrtimer_start_range_ns+0xff/0xc20 kernel/time/hrtimer.c:1284 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (hrtimer_bases.lock){-.-.}-{2:2}: __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0xb0/0x100 kernel/locking/spinlock.c:162 lock_hrtimer_base kernel/time/hrtimer.c:168 [inline] hrtimer_start_range_ns+0xff/0xc20 kernel/time/hrtimer.c:1284 hrtimer_start include/linux/hrtimer.h:420 [inline] run_page_cache_worker kernel/rcu/tree.c:3492 [inline] kvfree_call_rcu+0x61b/0x7d0 kernel/rcu/tree.c:3603 rtnl_register_internal+0x489/0x590 net/core/rtnetlink.c:225 rtnl_register+0x2e/0x70 net/core/rtnetlink.c:275 ip_rt_init+0x2e0/0x3a0 net/ipv4/route.c:3803 ip_init+0xa/0x20 net/ipv4/ip_output.c:1750 inet_init+0x28b/0x3a0 net/ipv4/af_inet.c:2007 do_one_initcall+0x272/0x730 init/main.c:1316 do_initcall_level+0x137/0x1f0 init/main.c:1389 do_initcalls+0x4b/0x90 init/main.c:1405 kernel_init_freeable+0x3e9/0x570 init/main.c:1629 kernel_init+0x19/0x1b0 init/main.c:1520 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287 -> #1 (krc.lock){....}-{2:2}: __raw_spin_lock include/linux/spinlock_api_smp.h:142 [inline] _raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154 krc_this_cpu_lock kernel/rcu/tree.c:3203 [inline] add_ptr_to_bulk_krc_lock kernel/rcu/tree.c:3510 [inline] kvfree_call_rcu+0x18d/0x7d0 kernel/rcu/tree.c:3601 trie_update_elem+0x86c/0xc50 kernel/bpf/lpm_trie.c:396 bpf_map_update_value+0x57d/0x650 kernel/bpf/syscall.c:223 generic_map_update_batch+0x52d/0x7d0 kernel/bpf/syscall.c:1430 bpf_map_do_batch+0x466/0x600 kernel/bpf/syscall.c:-1 __sys_bpf+0x671/0x6f0 kernel/bpf/syscall.c:-1 __do_sys_bpf kernel/bpf/syscall.c:4761 [inline] __se_sys_bpf kernel/bpf/syscall.c:4759 [inline] __x64_sys_bpf+0x78/0x90 kernel/bpf/syscall.c:4759 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #0 (&trie->lock){....}-{2:2}: check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain kernel/locking/lockdep.c:3788 [inline] __lock_acquire+0x2c42/0x7d10 kernel/locking/lockdep.c:5012 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0xb0/0x100 kernel/locking/spinlock.c:162 trie_delete_elem+0x90/0x710 kernel/bpf/lpm_trie.c:467 bpf_prog_e6a446e6ec7b690a+0x40/0x780 bpf_dispatcher_nop_func include/linux/bpf.h:888 [inline] __bpf_prog_run include/linux/filter.h:621 [inline] bpf_prog_run include/linux/filter.h:635 [inline] __bpf_trace_run kernel/trace/bpf_trace.c:1878 [inline] bpf_trace_run2+0x252/0x2e0 kernel/trace/bpf_trace.c:1915 trace_hrtimer_start include/trace/events/timer.h:199 [inline] debug_activate kernel/time/hrtimer.c:466 [inline] enqueue_hrtimer+0x314/0x370 kernel/time/hrtimer.c:1069 __hrtimer_start_range_ns kernel/time/hrtimer.c:1244 [inline] hrtimer_start_range_ns+0xa7e/0xc20 kernel/time/hrtimer.c:1286 futex_wait_queue_me+0x18c/0x440 kernel/futex/core.c:2850 futex_wait+0x256/0x680 kernel/futex/core.c:2964 do_futex+0xdb2/0x12b0 kernel/futex/core.c:3982 __do_sys_futex kernel/futex/core.c:4059 [inline] __se_sys_futex+0x389/0x420 kernel/futex/core.c:4040 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 other info that might help us debug this: Chain exists of: &trie->lock --> krc.lock --> hrtimer_bases.lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(hrtimer_bases.lock); lock(krc.lock); lock(hrtimer_bases.lock); lock(&trie->lock); *** DEADLOCK *** 2 locks held by syz.3.39/4404: #0: ffff8880b902a258 (hrtimer_bases.lock){-.-.}-{2:2}, at: lock_hrtimer_base kernel/time/hrtimer.c:168 [inline] #0: ffff8880b902a258 (hrtimer_bases.lock){-.-.}-{2:2}, at: hrtimer_start_range_ns+0xff/0xc20 kernel/time/hrtimer.c:1284 #1: ffffffff8c31eaa0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x5/0x30 include/linux/rcupdate.h:312 stack backtrace: CPU: 0 PID: 4404 Comm: syz.3.39 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025 Call Trace: dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106 check_noncircular+0x296/0x330 kernel/locking/lockdep.c:2133 check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain kernel/locking/lockdep.c:3788 [inline] __lock_acquire+0x2c42/0x7d10 kernel/locking/lockdep.c:5012 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0xb0/0x100 kernel/locking/spinlock.c:162 trie_delete_elem+0x90/0x710 kernel/bpf/lpm_trie.c:467 bpf_prog_e6a446e6ec7b690a+0x40/0x780 bpf_dispatcher_nop_func include/linux/bpf.h:888 [inline] __bpf_prog_run include/linux/filter.h:621 [inline] bpf_prog_run include/linux/filter.h:635 [inline] __bpf_trace_run kernel/trace/bpf_trace.c:1878 [inline] bpf_trace_run2+0x252/0x2e0 kernel/trace/bpf_trace.c:1915 trace_hrtimer_start include/trace/events/timer.h:199 [inline] debug_activate kernel/time/hrtimer.c:466 [inline] enqueue_hrtimer+0x314/0x370 kernel/time/hrtimer.c:1069 __hrtimer_start_range_ns kernel/time/hrtimer.c:1244 [inline] hrtimer_start_range_ns+0xa7e/0xc20 kernel/time/hrtimer.c:1286 futex_wait_queue_me+0x18c/0x440 kernel/futex/core.c:2850 futex_wait+0x256/0x680 kernel/futex/core.c:2964 do_futex+0xdb2/0x12b0 kernel/futex/core.c:3982 __do_sys_futex kernel/futex/core.c:4059 [inline] __se_sys_futex+0x389/0x420 kernel/futex/core.c:4040 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 RIP: 0033:0x7ff94b3cacb9 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffdf618aee8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca RAX: ffffffffffffffda RBX: 0000000000011499 RCX: 00007ff94b3cacb9 RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007ff94b645fac RBP: 0000000000000226 R08: 002f9e9b25d66196 R09: 0000000000000000 R10: 00007ffdf618aff0 R11: 0000000000000246 R12: 00007ffdf618b010 R13: 00007ff94b645fac R14: 00000000000116bf R15: 00007ffdf618aff0