============================================
WARNING: possible recursive locking detected
5.15.183-syzkaller #0 Not tainted
--------------------------------------------
kworker/0:5/4230 is trying to acquire lock:
ffff88807e26a218 (dev->qdisc_tx_busylock ?: &qdisc_tx_busylock){+...}-{2:2}, at: spin_lock include/linux/spinlock.h:363 [inline]
ffff88807e26a218 (dev->qdisc_tx_busylock ?: &qdisc_tx_busylock){+...}-{2:2}, at: __dev_xmit_skb net/core/dev.c:3909 [inline]
ffff88807e26a218 (dev->qdisc_tx_busylock ?: &qdisc_tx_busylock){+...}-{2:2}, at: __dev_queue_xmit+0x1f6e/0x2ed0 net/core/dev.c:4253

but task is already holding lock:
ffff888020198258 (dev->qdisc_tx_busylock ?: &qdisc_tx_busylock){+...}-{2:2}, at: spin_trylock include/linux/spinlock.h:373 [inline]
ffff888020198258 (dev->qdisc_tx_busylock ?: &qdisc_tx_busylock){+...}-{2:2}, at: qdisc_run_begin include/net/sch_generic.h:173 [inline]
ffff888020198258 (dev->qdisc_tx_busylock ?: &qdisc_tx_busylock){+...}-{2:2}, at: __dev_xmit_skb net/core/dev.c:3871 [inline]
ffff888020198258 (dev->qdisc_tx_busylock ?: &qdisc_tx_busylock){+...}-{2:2}, at: __dev_queue_xmit+0x10b9/0x2ed0 net/core/dev.c:4253

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(dev->qdisc_tx_busylock ?: &qdisc_tx_busylock
);
  lock(dev->qdisc_tx_busylock ?: &qdisc_tx_busylock
);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

9 locks held by kworker/0:5/4230:
 #0: ffff88802aeca138 (
(wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
 #1: ffffc900031ffd00 ((work_completion)(&(&ifa->dad_work)->work)
){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
 #2: ffffffff8d22a388 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_dad_work+0xc4/0x1520 net/ipv6/addrconf.c:4116
 #3: ffffffff8c11bea0 (rcu_read_lock
){....}-{1:2}, at: rcu_lock_acquire+0x5/0x30 include/linux/rcupdate.h:311
 #4: ffffffff8c11bf00 (rcu_read_lock_bh){....}-{1:2}, at: rcu_lock_acquire+0x9/0x30 include/linux/rcupdate.h:312
 #5: ffffffff8c11bf00 (rcu_read_lock_bh){....}-{1:2}, at: rcu_lock_acquire+0x9/0x30 include/linux/rcupdate.h:312
 #6: ffff888020198258 (dev->qdisc_tx_busylock ?: &qdisc_tx_busylock){+...}-{2:2}, at: spin_trylock include/linux/spinlock.h:373 [inline]
 #6: ffff888020198258 (dev->qdisc_tx_busylock ?: &qdisc_tx_busylock){+...}-{2:2}, at: qdisc_run_begin include/net/sch_generic.h:173 [inline]
 #6: ffff888020198258 (dev->qdisc_tx_busylock ?: &qdisc_tx_busylock){+...}-{2:2}, at: __dev_xmit_skb net/core/dev.c:3871 [inline]
 #6: ffff888020198258 (dev->qdisc_tx_busylock ?: &qdisc_tx_busylock){+...}-{2:2}, at: __dev_queue_xmit+0x10b9/0x2ed0 net/core/dev.c:4253
 #7: ffffffff8c11bf00 (rcu_read_lock_bh){....}-{1:2}, at: rcu_lock_acquire+0x9/0x30 include/linux/rcupdate.h:312
 #8: ffffffff8c11bf00 (rcu_read_lock_bh){....}-{1:2}, at: rcu_lock_acquire+0x9/0x30 include/linux/rcupdate.h:312

stack backtrace:
CPU: 0 PID: 4230 Comm: kworker/0:5 Not tainted 5.15.183-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
Workqueue: ipv6_addrconf addrconf_dad_work

Call Trace:
 <TASK>
 dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
 __lock_acquire+0x1227/0x7c60 kernel/locking/lockdep.c:-1
 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
 __raw_spin_lock include/linux/spinlock_api_smp.h:142 [inline]
 _raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154
 spin_lock include/linux/spinlock.h:363 [inline]
 __dev_xmit_skb net/core/dev.c:3909 [inline]
 __dev_queue_xmit+0x1f6e/0x2ed0 net/core/dev.c:4253
 neigh_hh_output include/net/neighbour.h:493 [inline]
 neigh_output include/net/neighbour.h:507 [inline]
 ip_finish_output2+0xc69/0x1080 net/ipv4/ip_output.c:228
 iptunnel_xmit+0x525/0x960 net/ipv4/ip_tunnel_core.c:82
 ip_tunnel_xmit+0x1b6f/0x2240 net/ipv4/ip_tunnel.c:838
 __gre_xmit net/ipv4/ip_gre.c:474 [inline]
 gre_tap_xmit+0x4f9/0x6e0 net/ipv4/ip_gre.c:751
 __netdev_start_xmit include/linux/netdevice.h:5027 [inline]
 netdev_start_xmit include/linux/netdevice.h:5041 [inline]
 xmit_one net/core/dev.c:3649 [inline]
 dev_hard_start_xmit+0x2a5/0x7e0 net/core/dev.c:3665
 sch_direct_xmit+0x24e/0x4a0 net/sched/sch_generic.c:342
 __dev_xmit_skb net/core/dev.c:3884 [inline]
 __dev_queue_xmit+0x170e/0x2ed0 net/core/dev.c:4253
 neigh_output include/net/neighbour.h:509 [inline]
 ip6_finish_output2+0x1070/0x1500 net/ipv6/ip6_output.c:130
 dst_output include/net/dst.h:452 [inline]
 NF_HOOK include/linux/netfilter.h:302 [inline]
 ndisc_send_skb+0xbea/0x14a0 net/ipv6/ndisc.c:513
 ndisc_send_ns+0x63c/0x840 net/ipv6/ndisc.c:655
 addrconf_dad_work+0xa47/0x1520 net/ipv6/addrconf.c:4204
 process_one_work+0x863/0x1000 kernel/workqueue.c:2310
 worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457
 kthread+0x436/0x520 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>
GRED: Unable to relocate VQ 0x0 after dequeue, screwing up backlog
GRED: Unable to relocate VQ 0x0 after dequeue, screwing up backlog