============================= WARNING: suspicious RCU usage syzkaller #0 Not tainted ----------------------------- net/sched/sch_api.c:304 suspicious rcu_dereference_protected() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 3 locks held by ksoftirqd/1/20: #0: ffffc90000da7a80 ((&q->perturb_timer)){+.-.}-{0:0}, at: lockdep_copy_map include/linux/lockdep.h:45 [inline] #0: ffffc90000da7a80 ((&q->perturb_timer)){+.-.}-{0:0}, at: call_timer_fn+0xca/0x540 kernel/time/timer.c:1638 #1: ffff88801fc4b108 (&sch->q.lock){+.-.}-{2:2}, at: spin_lock include/linux/spinlock.h:364 [inline] #1: ffff88801fc4b108 (&sch->q.lock){+.-.}-{2:2}, at: sfq_perturbation+0x14d/0x2090 net/sched/sch_sfq.c:610 #2: ffffffff8c31ef20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x5/0x30 include/linux/rcupdate.h:312 stack backtrace: CPU: 1 PID: 20 Comm: ksoftirqd/1 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/25/2026 Call Trace: dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106 qdisc_lookup+0xa6/0x640 net/sched/sch_api.c:304 qdisc_tree_reduce_backlog+0x188/0x480 net/sched/sch_api.c:783 sfq_rehash net/sched/sch_sfq.c:598 [inline] sfq_perturbation+0x1f26/0x2090 net/sched/sch_sfq.c:613 call_timer_fn+0x17b/0x540 kernel/time/timer.c:1648 expire_timers kernel/time/timer.c:1699 [inline] __run_timers+0x56c/0x810 kernel/time/timer.c:1970 handle_softirqs+0x336/0x830 kernel/softirq.c:576 run_ksoftirqd+0xa4/0x100 kernel/softirq.c:943 smpboot_thread_fn+0x520/0x990 kernel/smpboot.c:164 kthread+0x42e/0x520 kernel/kthread.c:334 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287