======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
kworker/u8:0/12 is trying to acquire lock:
ffff888021409070 (&hsr->seqnr_lock){+.-.}-{3:3}, at: hsr_dev_xmit+0x237/0x360

but task is already holding lock:
ffff888115bd0158 (&qdisc_xmit_lock_key#3){+.-.}-{3:3}, at: sch_direct_xmit+0x15f/0x4c0

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&qdisc_xmit_lock_key#3){+.-.}-{3:3}:
       _raw_spin_lock+0x2e/0x40
       sch_direct_xmit+0x15f/0x4c0
       __dev_queue_xmit+0x177f/0x3820
       hsr_forward_skb+0x152a/0x28c0
       send_hsr_supervision_frame+0x733/0xcf0
       hsr_announce+0x1db/0x370
       call_timer_fn+0x192/0x5e0
       __run_timer_base+0x652/0x8b0
       run_timer_softirq+0xb7/0x170
       handle_softirqs+0x225/0x840
       __irq_exit_rcu+0xca/0x220
       irq_exit_rcu+0x9/0x30
       sysvec_apic_timer_interrupt+0xa6/0xc0
       asm_sysvec_apic_timer_interrupt+0x1a/0x20
       __sanitizer_cov_trace_const_cmp4+0x10/0x90
       page_ext_lookup+0xf2/0x180
       page_table_check_clear+0x212/0x500
       __zap_vma_range+0x39bb/0x4f10
       unmap_vmas+0x390/0x550
       exit_mmap+0x293/0x9f0
       __mmput+0x118/0x420
       exit_mm+0x221/0x2d0
       do_exit+0x6cd/0x2360
       do_group_exit+0x22d/0x2f0
       __x64_sys_exit_group+0x3f/0x40
       x64_sys_call+0x221a/0x2240
       do_syscall_64+0x174/0x580
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&hsr->seqnr_lock){+.-.}-{3:3}:
       __lock_acquire+0x1520/0x2cf0
       lock_acquire+0x106/0x350
       _raw_spin_lock_bh+0x36/0x50
       hsr_dev_xmit+0x237/0x360
       dev_hard_start_xmit+0x2cd/0x830
       __dev_queue_xmit+0x14c0/0x3820
       NF_HOOK+0x33a/0x3c0
       arp_xmit+0x16c/0x270
       arp_solicit+0xbdc/0xe40
       __neigh_event_send+0xf0c/0x1510
       neigh_resolve_output+0x1a1/0x720
       ip_finish_output2+0xc4b/0x10b0
       ip_output+0x29f/0x450
       iptunnel_xmit+0x626/0xd10
       ip_tunnel_xmit+0x195b/0x2040
       __gre_xmit+0x19e/0x240
       erspan_xmit+0xad5/0x1590
       dev_hard_start_xmit+0x2cd/0x830
       sch_direct_xmit+0x257/0x4c0
       __dev_queue_xmit+0x177f/0x3820
       alb_send_lp_vid+0x348/0x550
       alb_send_learning_packets+0x12c/0x300
       bond_alb_monitor+0x3d0/0x17c0
       process_scheduled_works+0xa8e/0x14e0
       worker_thread+0xa47/0xfb0
       kthread+0x388/0x470
       ret_from_fork+0x514/0xb70
       ret_from_fork_asm+0x1a/0x30

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&qdisc_xmit_lock_key#3);
                               lock(&hsr->seqnr_lock);
                               lock(&qdisc_xmit_lock_key#3);
  lock(&hsr->seqnr_lock);

 *** DEADLOCK ***

11 locks held by kworker/u8:0/12:
 #0: ffff888022b06140 ((wq_completion)bond86){+.+.}-{0:0}, at: process_scheduled_works+0xa20/0x14e0
 #1: ffffc90000117c40 ((work_completion)(&(&bond->alb_work)->work)){+.+.}-{0:0}, at: process_scheduled_works+0xa20/0x14e0
 #2: ffffffff8eb59c60 (rcu_read_lock){....}-{1:3}, at: bond_alb_monitor+0xf3/0x17c0
 #3: ffffffff8eb59cc0 (rcu_read_lock_bh){....}-{1:3}, at: __dev_queue_xmit+0x29b/0x3820
 #4: ffff88811551b228 (dev->qdisc_tx_busylock ?: &qdisc_tx_busylock#5){+...}-{3:3}, at: __dev_queue_xmit+0x1143/0x3820
 #5: ffff888115bd0158 (&qdisc_xmit_lock_key#3){+.-.}-{3:3}, at: sch_direct_xmit+0x15f/0x4c0
 #6: ffffffff8eb59c60 (rcu_read_lock){....}-{1:3}, at: ip_output+0x5a/0x450
 #7: ffffffff8eb59c60 (rcu_read_lock){....}-{1:3}, at: ip_finish_output2+0x3de/0x10b0
 #8: ffffffff8eb59c60 (rcu_read_lock){....}-{1:3}, at: arp_xmit+0x23/0x270
 #9: ffffffff8eb59cc0 (rcu_read_lock_bh){....}-{1:3}, at: __dev_queue_xmit+0x29b/0x3820
 #10: ffffffff8eb59c60 (rcu_read_lock){....}-{1:3}, at: hsr_dev_xmit+0x2d/0x360

stack backtrace:
CPU: 1 UID: 0 PID: 12 Comm: kworker/u8:0 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Workqueue: bond86 bond_alb_monitor
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150
 print_circular_bug+0x2e1/0x300
 check_noncircular+0x12e/0x150
 __lock_acquire+0x1520/0x2cf0
 lock_acquire+0x106/0x350
 _raw_spin_lock_bh+0x36/0x50
 hsr_dev_xmit+0x237/0x360
 dev_hard_start_xmit+0x2cd/0x830
 __dev_queue_xmit+0x14c0/0x3820
 NF_HOOK+0x33a/0x3c0
 arp_xmit+0x16c/0x270
 arp_solicit+0xbdc/0xe40
 __neigh_event_send+0xf0c/0x1510
 neigh_resolve_output+0x1a1/0x720
 ip_finish_output2+0xc4b/0x10b0
 ip_output+0x29f/0x450
 iptunnel_xmit+0x626/0xd10
 ip_tunnel_xmit+0x195b/0x2040
 __gre_xmit+0x19e/0x240
 erspan_xmit+0xad5/0x1590
 dev_hard_start_xmit+0x2cd/0x830
 sch_direct_xmit+0x257/0x4c0
 __dev_queue_xmit+0x177f/0x3820
 alb_send_lp_vid+0x348/0x550
 alb_send_learning_packets+0x12c/0x300
 bond_alb_monitor+0x3d0/0x17c0
 process_scheduled_works+0xa8e/0x14e0
 worker_thread+0xa47/0xfb0
 kthread+0x388/0x470
 ret_from_fork+0x514/0xb70
 ret_from_fork_asm+0x1a/0x30
 </TASK>
bond90: (slave bridge23): failed to get link speed/duplex
net_ratelimit: 47 callbacks suppressed
bond90: (slave bridge23): failed to get link speed/duplex
