possible deadlock in sch_direct_xmit (6)

Status: upstream: reported on 2026/05/10 19:12
Subsystems: net
Labels: prio:normal
[Documentation on labels]
Reported-by: syzbot+9bda1b9fbb7fbdf9b62b@syzkaller.appspotmail.com
Fix commit: net: erspan: set lltx to avoid sch_direct_xmit deadlock
Patched on: [ci-upstream-linux-next-kasan-gce-root ci-upstream-net-this-kasan-gce ci-upstream-rust-kasan-gce], missing on: [ci-qemu-gce-upstream-auto ci-qemu-native-arm64-kvm ci-qemu-upstream ci-qemu-upstream-386 ci-qemu2-arm32 ci-qemu2-arm64 ci-qemu2-arm64-compat ci-qemu2-arm64-mte ci-qemu2-riscv64 ci-snapshot-upstream-root ci-upstream-bpf-kasan-gce ci-upstream-bpf-next-kasan-gce ci-upstream-gce-arm64 ci-upstream-gce-leak ci-upstream-kasan-badwrites-root ci-upstream-kasan-gce ci-upstream-kasan-gce-386 ci-upstream-kasan-gce-root ci-upstream-kasan-gce-selinux-root ci-upstream-kasan-gce-smack-root ci-upstream-kmsan-gce-386-root ci-upstream-kmsan-gce-root ci-upstream-net-kasan-gce ci2-upstream-fs ci2-upstream-kcsan-gce ci2-upstream-usb]
First crash: 164d, last: 18h10m
▶ ▼ ✨ AI Jobs (1)
ID Workflow Result Correct Bug Created Started Finished Revision
53426d40 assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ❌ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ❌ UserNamespace: ✅ VMGuestTrigger: ❌ VMHostTrigger: ❌ ❓ possible deadlock in sch_direct_xmit (6) 2026/05/17 15:20 2026/05/17 15:20 2026/05/17 16:17 de5aae85
▶ ▼ Discussions (7)
Title Replies (including bot) Last reply
[PATCH net v5] net: erspan: set lltx to avoid sch_direct_xmit deadlock 2 (2) 2026/10/12 10:37
[PATCH net v4] net: erspan: set lltx to avoid sch_direct_xmit deadlock 4 (4) 2026/09/21 10:46
[PATCH net v3] net: erspan: set lltx to avoid sch_direct_xmit deadlock 2 (2) 2026/08/03 15:11
[PATCH net v2] net: erspan: set lltx to avoid sch_direct_xmit deadlock 4 (4) 2026/07/20 08:26
[PATCH] net: erspan: set lltx to avoid sch_direct_xmit deadlock 3 (3) 2026/07/09 09:18
[PATCH] net: erspan: set lltx to avoid sch_direct_xmit deadlock 2 (2) 2026/07/09 06:57
[syzbot] [net?] possible deadlock in sch_direct_xmit (6) 0 (1) 2026/05/10 19:12
▶ ▼ Similar bugs (15)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 possible deadlock in sch_direct_xmit (2) origin:lts-only 4 syz, C done 32 45d 1012d 0/3 upstream: reported C repro on 2024/01/09 18:28
android-44 possible deadlock in sch_direct_xmit 4 syz, C 240 2510d 2747d 0/2 public: reported C repro on 2019/04/11 08:44
upstream possible deadlock in sch_direct_xmit (2) net 4 syz, C done unreliable 109 1189d 2363d 0/29 auto-obsoleted due to no activity on 2024/01/14 06:05
linux-4.19 possible deadlock in sch_direct_xmit (2) 4 syz, C error 15 1331d 1848d 0/1 upstream: reported C repro on 2021/09/26 01:30
upstream possible deadlock in sch_direct_xmit net 4 syz, C done done 1548 2518d 3196d 15/29 fixed on 2020/04/17 19:57
linux-5.15 possible deadlock in sch_direct_xmit (2) origin:lts-only 4 syz, C error 22 5h35m 968d 0/3 upstream: reported C repro on 2024/02/22 19:25
linux-4.14 possible deadlock in sch_direct_xmit 4 1 2694d 2694d 0/1 auto-closed as invalid on 2019/10/25 08:40
upstream possible deadlock in sch_direct_xmit (4) net 4 1 903d 903d 25/29 fixed on 2024/06/05 13:52
upstream possible deadlock in sch_direct_xmit (5) net 4 syz, C unreliable 1245 164d 284d 29/29 fixed on 2026/05/06 16:40
linux-4.14 possible deadlock in sch_direct_xmit (2) 4 1 2527d 2527d 0/1 auto-closed as invalid on 2020/03/15 19:58
linux-4.19 possible deadlock in sch_direct_xmit 4 1 2695d 2695d 0/1 auto-closed as invalid on 2019/10/25 08:50
linux-5.15 possible deadlock in sch_direct_xmit 4 1 1255d 1255d 0/3 auto-obsoleted due to no activity on 2023/08/23 09:09
linux-6.1 possible deadlock in sch_direct_xmit 4 2 1263d 1302d 0/3 auto-obsoleted due to no activity on 2023/08/23 09:10
upstream possible deadlock in sch_direct_xmit (3) net 4 1 979d 979d 25/29 fixed on 2024/04/10 16:40
linux-6.6 possible deadlock in sch_direct_xmit 4 4 170d 302d 0/2 auto-obsoleted due to no activity on 2026/08/08 18:35

Sample crash report:
============================================
WARNING: possible recursive locking detected
syzkaller #0 Tainted: G             L     
--------------------------------------------
kworker/u8:40/14418 is trying to acquire lock:
ffff88807aee1558 (&qdisc_xmit_lock_key#4){+.-.}-{3:3}, at: spin_lock include/linux/spinlock.h:347 [inline]
ffff88807aee1558 (&qdisc_xmit_lock_key#4){+.-.}-{3:3}, at: __netif_tx_lock include/linux/netdevice.h:4841 [inline]
ffff88807aee1558 (&qdisc_xmit_lock_key#4){+.-.}-{3:3}, at: sch_direct_xmit+0x15f/0x4c0 net/sched/sch_generic.c:370

but task is already holding lock:
ffff888064f21558 (&qdisc_xmit_lock_key#4){+.-.}-{3:3}, at: spin_lock include/linux/spinlock.h:347 [inline]
ffff888064f21558 (&qdisc_xmit_lock_key#4){+.-.}-{3:3}, at: __netif_tx_lock include/linux/netdevice.h:4841 [inline]
ffff888064f21558 (&qdisc_xmit_lock_key#4){+.-.}-{3:3}, at: sch_direct_xmit+0x15f/0x4c0 net/sched/sch_generic.c:370

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

       CPU0
       ----
  lock(&qdisc_xmit_lock_key#4);
  lock(&qdisc_xmit_lock_key#4);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

locks held by kworker/u8:40/14418: 10, last CPU#1:
 #0: ffff88804fcc3940 ((wq_completion)bond1#2){+.+.}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:309 [inline]
 #0: ffff88804fcc3940 ((wq_completion)bond1#2){+.+.}-{0:0}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline]
 #0: ffff88804fcc3940 ((wq_completion)bond1#2){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3361 [inline]
 #0: ffff88804fcc3940 ((wq_completion)bond1#2){+.+.}-{0:0}, at: process_scheduled_works+0x97a/0x1630 kernel/workqueue.c:3479
 #1: ffffc90005247c40 ((work_completion)(&(&bond->alb_work)->work)){+.+.}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:309 [inline]
 #1: ffffc90005247c40 ((work_completion)(&(&bond->alb_work)->work)){+.+.}-{0:0}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline]
 #1: ffffc90005247c40 ((work_completion)(&(&bond->alb_work)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3361 [inline]
 #1: ffffc90005247c40 ((work_completion)(&(&bond->alb_work)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x97a/0x1630 kernel/workqueue.c:3479
 #2: ffffffff8fd5c8e0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:309 [inline]
 #2: ffffffff8fd5c8e0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline]
 #2: ffffffff8fd5c8e0 (rcu_read_lock){....}-{1:3}, at: bond_alb_monitor+0xf3/0x1820 drivers/net/bonding/bond_alb.c:1552
 #3: ffffffff8fd5c940 (rcu_read_lock_bh){....}-{1:3}, at: local_bh_disable include/linux/bottom_half.h:20 [inline]
 #3: ffffffff8fd5c940 (rcu_read_lock_bh){....}-{1:3}, at: rcu_read_lock_bh include/linux/rcupdate.h:902 [inline]
 #3: ffffffff8fd5c940 (rcu_read_lock_bh){....}-{1:3}, at: __dev_queue_xmit+0x29b/0x3920 net/core/dev.c:4872
 #4: ffff888078ce2228 (dev->qdisc_tx_busylock ?: &qdisc_tx_busylock#5){+...}-{3:3}, at: spin_trylock include/linux/spinlock.h:359 [inline]
 #4: ffff888078ce2228 (dev->qdisc_tx_busylock ?: &qdisc_tx_busylock#5){+...}-{3:3}, at: qdisc_run_begin include/net/sch_generic.h:206 [inline]
 #4: ffff888078ce2228 (dev->qdisc_tx_busylock ?: &qdisc_tx_busylock#5){+...}-{3:3}, at: __dev_xmit_skb net/core/dev.c:4264 [inline]
 #4: ffff888078ce2228 (dev->qdisc_tx_busylock ?: &qdisc_tx_busylock#5){+...}-{3:3}, at: __dev_queue_xmit+0x114e/0x3920 net/core/dev.c:4916
 #5: ffff888064f21558 (&qdisc_xmit_lock_key#4){+.-.}-{3:3}, at: spin_lock include/linux/spinlock.h:347 [inline]
 #5: ffff888064f21558 (&qdisc_xmit_lock_key#4){+.-.}-{3:3}, at: __netif_tx_lock include/linux/netdevice.h:4841 [inline]
 #5: ffff888064f21558 (&qdisc_xmit_lock_key#4){+.-.}-{3:3}, at: sch_direct_xmit+0x15f/0x4c0 net/sched/sch_generic.c:370
 #6: ffffffff8fd5c8e0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:309 [inline]
 #6: ffffffff8fd5c8e0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline]
 #6: ffffffff8fd5c8e0 (rcu_read_lock){....}-{1:3}, at: ip_output+0x5a/0x450 net/ipv4/ip_output.c:432
 #7: ffffffff8fd5c8e0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:309 [inline]
 #7: ffffffff8fd5c8e0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline]
 #7: ffffffff8fd5c8e0 (rcu_read_lock){....}-{1:3}, at: ip_finish_output2+0x3de/0x10b0 net/ipv4/ip_output.c:229
 #8: ffffffff8fd5c940 (rcu_read_lock_bh){....}-{1:3}, at: local_bh_disable include/linux/bottom_half.h:20 [inline]
 #8: ffffffff8fd5c940 (rcu_read_lock_bh){....}-{1:3}, at: rcu_read_lock_bh include/linux/rcupdate.h:902 [inline]
 #8: ffffffff8fd5c940 (rcu_read_lock_bh){....}-{1:3}, at: __dev_queue_xmit+0x29b/0x3920 net/core/dev.c:4872
 #9: ffff888051e22228 (dev->qdisc_tx_busylock ?: &qdisc_tx_busylock#5){+...}-{3:3}, at: spin_trylock include/linux/spinlock.h:359 [inline]
 #9: ffff888051e22228 (dev->qdisc_tx_busylock ?: &qdisc_tx_busylock#5){+...}-{3:3}, at: qdisc_run_begin include/net/sch_generic.h:206 [inline]
 #9: ffff888051e22228 (dev->qdisc_tx_busylock ?: &qdisc_tx_busylock#5){+...}-{3:3}, at: __dev_xmit_skb net/core/dev.c:4264 [inline]
 #9: ffff888051e22228 (dev->qdisc_tx_busylock ?: &qdisc_tx_busylock#5){+...}-{3:3}, at: __dev_queue_xmit+0x114e/0x3920 net/core/dev.c:4916

stack backtrace:
CPU: 1 UID: 0 PID: 14418 Comm: kworker/u8:40 Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/16/2026
Workqueue: bond1 bond_alb_monitor
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_deadlock_bug+0x27a/0x290 kernel/locking/lockdep.c:3085
 check_deadlock kernel/locking/lockdep.c:3137 [inline]
 validate_chain kernel/locking/lockdep.c:3939 [inline]
 __lock_acquire+0x25db/0x2de0 kernel/locking/lockdep.c:5288
 lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5942
 __raw_spin_lock include/linux/spinlock_api_smp.h:190 [inline]
 _raw_spin_lock+0x2e/0x40 kernel/locking/spinlock.c:173
 spin_lock include/linux/spinlock.h:347 [inline]
 __netif_tx_lock include/linux/netdevice.h:4841 [inline]
 sch_direct_xmit+0x15f/0x4c0 net/sched/sch_generic.c:370
 __dev_xmit_skb net/core/dev.c:4277 [inline]
 __dev_queue_xmit+0x179a/0x3920 net/core/dev.c:4916
 neigh_output include/net/neighbour.h:560 [inline]
 ip_finish_output2+0xc4b/0x10b0 net/ipv4/ip_output.c:236
 NF_HOOK_COND include/linux/netfilter.h:314 [inline]
 ip_output+0x29f/0x450 net/ipv4/ip_output.c:437
 iptunnel_xmit+0x626/0xd10 net/ipv4/ip_tunnel_core.c:97
 ip_tunnel_xmit+0x195b/0x2040 net/ipv4/ip_tunnel.c:848
 erspan_xmit+0xb6a/0x1620 net/ipv4/ip_gre.c:752
 __netdev_start_xmit include/linux/netdevice.h:5432 [inline]
 netdev_start_xmit include/linux/netdevice.h:5441 [inline]
 xmit_one net/core/dev.c:3953 [inline]
 dev_hard_start_xmit+0x2cd/0x830 net/core/dev.c:3969
 sch_direct_xmit+0x257/0x4c0 net/sched/sch_generic.c:372
 __dev_xmit_skb net/core/dev.c:4277 [inline]
 __dev_queue_xmit+0x179a/0x3920 net/core/dev.c:4916
 dev_queue_xmit include/linux/netdevice.h:3464 [inline]
 alb_send_lp_vid+0x348/0x550 drivers/net/bonding/bond_alb.c:955
 alb_send_learning_packets+0x12c/0x300 drivers/net/bonding/bond_alb.c:1018
 bond_alb_monitor+0x3d0/0x1820 drivers/net/bonding/bond_alb.c:1569
 process_one_work kernel/workqueue.c:3396 [inline]
 process_scheduled_works+0xc3d/0x1630 kernel/workqueue.c:3479
 worker_thread+0xa47/0xfb0 kernel/workqueue.c:3560
 kthread+0x38b/0x480 kernel/kthread.c:436
 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>

Crashes (322):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/10/13 13:27 upstream 24a19b953e2a 7321cd29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in sch_direct_xmit
2026/10/12 14:47 upstream 24a19b953e2a 745a967f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in sch_direct_xmit
2026/10/05 13:14 upstream a90ee4305c4a 1995e6c7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in sch_direct_xmit
2026/10/04 13:46 upstream 6addb4f38557 57bbd979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in sch_direct_xmit
2026/10/01 05:01 upstream 551c722f4080 38f7f0d1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in sch_direct_xmit
2026/09/27 12:36 upstream fd179f8a05be a3c7249d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in sch_direct_xmit
2026/09/18 05:54 upstream 5dd1818b15d9 8d7d05f1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in sch_direct_xmit
2026/09/08 17:41 upstream 28924df2a08f 243b72f1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in sch_direct_xmit
2026/08/15 20:23 upstream 15ef2f78c49d 746171ee .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in sch_direct_xmit
2026/07/05 22:57 upstream f105f3631d51 fcece630 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in sch_direct_xmit
2026/05/17 09:55 upstream 6916d5703ddf de5aae85 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in sch_direct_xmit
2026/05/09 08:12 upstream 70390501d194 29233ece .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in sch_direct_xmit
2026/10/11 03:41 upstream a5ebb76233b7 4f92358f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in sch_direct_xmit
2026/09/22 18:28 upstream 50d05c7c76c9 3e2106e5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in sch_direct_xmit
2026/09/18 17:13 upstream 50d05c7c76c9 8d7d05f1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in sch_direct_xmit
2026/09/10 20:59 upstream 50d05c7c76c9 1fe56c0a .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in sch_direct_xmit
2026/08/22 17:27 upstream 66fb95a52111 1e72964b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in sch_direct_xmit
2026/10/10 20:42 net af32da41b032 4f92358f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in sch_direct_xmit
2026/09/28 10:56 net a7bfaba4823e a3c7249d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in sch_direct_xmit
2026/09/18 15:19 net 3b95a04eb5f9 8d7d05f1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in sch_direct_xmit
2026/10/17 17:12 net-next 98c2ad4f5d80 432c0077 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/10/16 05:21 net-next 73022f605c44 3f2522c6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/10/15 19:33 net-next 73022f605c44 3f2522c6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/10/14 17:47 net-next 05b5019b01fb 7321cd29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/10/14 06:45 net-next 05b5019b01fb 7321cd29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/10/13 15:14 net-next d7804253678e 7321cd29 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/10/13 05:53 net-next d0bd617658dd 745a967f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/10/12 23:21 net-next 3a82195416fd 745a967f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/10/12 11:39 net-next d8674294aefe 4f92358f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/10/07 11:27 net-next 45ad84d2800e f7710056 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/10/06 13:02 net-next c0402d7640a8 f7710056 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/10/05 15:36 net-next 8b4e7209c842 1995e6c7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/10/04 21:15 net-next cfb7793d1bc0 57bbd979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/10/04 07:50 net-next cfb7793d1bc0 57bbd979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/10/02 22:12 net-next 071876fd5048 57bbd979 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/09/30 15:38 net-next 47a144672573 892a21ec .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/09/30 12:27 net-next 47a144672573 892a21ec .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/09/30 10:13 net-next 47a144672573 7808aef4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/09/30 00:47 net-next 6e23f90f2b8c 7808aef4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/09/28 16:42 net-next 014d795c7383 a3c7249d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/09/28 12:37 net-next 014d795c7383 a3c7249d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/09/27 05:45 net-next 014d795c7383 a3c7249d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/09/23 20:34 net-next 944ae66642b7 0a1606bc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/09/22 16:23 net-next eabc76156e86 3e2106e5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/09/22 05:14 net-next 2fba93180872 e12281bd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/09/21 06:26 net-next 8830e65ed46d 853b104b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/09/21 02:48 net-next a4e22e9253e7 853b104b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/09/20 10:45 net-next a4e22e9253e7 853b104b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/09/20 02:04 net-next a4e22e9253e7 853b104b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/09/18 22:37 net-next 4bb9710c6a68 8d7d05f1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/09/17 11:19 net-next 7bc21b740291 95928915 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/09/16 08:15 net-next b8e9e7d82e7e 12a0a44a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/09/16 00:26 net-next b8e9e7d82e7e 81a27d1a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/05/06 19:04 net-next 2281958e6007 cbcd9ea0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sch_direct_xmit
2026/08/12 23:49 linux-next 28d012efb432 7ae4acc7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in sch_direct_xmit
* Struck through repros no longer work on HEAD.