syzbot


possible deadlock in j1939_sk_errqueue

Status: fixed on 2023/06/08 14:41
Subsystems: can
[Documentation on labels]
Reported-by: syzbot+ee1cd780f69483a8616b@syzkaller.appspotmail.com
Fix commit: d1366b283d94 can: j1939: prevent deadlock by moving j1939_sk_errqueue()
First crash: 897d, last: 356d
Cause bisection: introduced by (bisect log) [no-op commit]:
commit 873a1e3d207ae587a7a1cc1d84545146b449ea5d
Author: Harman Kalra <hkalra@marvell.com>
Date: Tue Jun 29 17:00:04 2021 +0000

  octeontx2-af: cn10k: Setting up lmtst map table

Crash: KASAN: use-after-free Read in j1939_xtp_rx_dat_one (log)
Repro: C syz .config
  
Discussions (3)
Title Replies (including bot) Last reply
[PATCH net 0/2] pull-request: can 2023-03-27 4 (4) 2023/03/28 02:50
[PATCH v1] can: j1939: prevent deadlock by moving j1939_sk_errqueue() 1 (1) 2023/03/24 13:01
[syzbot] possible deadlock in j1939_sk_errqueue 0 (2) 2022/06/14 22:53
Similar bugs (3)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 possible deadlock in j1939_sk_errqueue origin:upstream C error 6 59d 234d 0/3 upstream: reported C repro on 2023/07/28 13:47
linux-6.1 possible deadlock in j1939_sk_errqueue origin:upstream C inconclusive 6 25d 254d 0/3 upstream: reported C repro on 2023/07/09 02:39
upstream possible deadlock in j1939_sk_errqueue (2) can C done 24 32d 259d 25/26 upstream: reported C repro on 2023/07/04 06:19
Last patch testing requests (1)
Created Duration User Patch Repo Result
2022/06/15 11:09 15m hdanton@sina.com patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 24625f7d91fb OK log

Sample crash report:
vcan0: j1939_tp_rxtimer: 0xffff88814717a000: rx timeout, send abort
vcan0: j1939_tp_rxtimer: 0xffff88807b7b3800: rx timeout, send abort
======================================================
WARNING: possible circular locking dependency detected
5.19.0-rc2-syzkaller-00049-g24625f7d91fb #0 Not tainted
------------------------------------------------------
swapper/0/0 is trying to acquire lock:
ffff8880777290d0 (&priv->j1939_socks_lock){+.-.}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:354 [inline]
ffff8880777290d0 (&priv->j1939_socks_lock){+.-.}-{2:2}, at: j1939_sk_errqueue+0x9f/0x1a0 net/can/j1939/socket.c:1078

but task is already holding lock:
ffff888077729088 (&priv->active_session_list_lock){+.-.}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:354 [inline]
ffff888077729088 (&priv->active_session_list_lock){+.-.}-{2:2}, at: j1939_session_list_lock net/can/j1939/transport.c:238 [inline]
ffff888077729088 (&priv->active_session_list_lock){+.-.}-{2:2}, at: j1939_tp_rxtimer+0xe5/0x220 net/can/j1939/transport.c:1240

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&priv->active_session_list_lock){+.-.}-{2:2}:
       __raw_spin_lock_bh include/linux/spinlock_api_smp.h:126 [inline]
       _raw_spin_lock_bh+0x2f/0x40 kernel/locking/spinlock.c:178
       spin_lock_bh include/linux/spinlock.h:354 [inline]
       j1939_session_list_lock net/can/j1939/transport.c:238 [inline]
       j1939_session_activate+0x43/0x4b0 net/can/j1939/transport.c:1553
       j1939_sk_queue_activate_next_locked net/can/j1939/socket.c:181 [inline]
       j1939_sk_queue_activate_next+0x29b/0x460 net/can/j1939/socket.c:205
       j1939_session_deactivate_activate_next net/can/j1939/transport.c:1101 [inline]
       j1939_session_completed+0x19a/0x1f0 net/can/j1939/transport.c:1214
       j1939_xtp_rx_eoma_one net/can/j1939/transport.c:1384 [inline]
       j1939_xtp_rx_eoma+0x2a6/0x5f0 net/can/j1939/transport.c:1399
       j1939_tp_cmd_recv net/can/j1939/transport.c:2088 [inline]
       j1939_tp_recv+0x930/0xcb0 net/can/j1939/transport.c:2133
       j1939_can_recv+0x6ff/0x9a0 net/can/j1939/main.c:108
       deliver net/can/af_can.c:574 [inline]
       can_rcv_filter+0x5d4/0x8d0 net/can/af_can.c:608
       can_receive+0x31d/0x580 net/can/af_can.c:665
       can_rcv+0x120/0x1c0 net/can/af_can.c:696
       __netif_receive_skb_one_core+0x114/0x180 net/core/dev.c:5478
       __netif_receive_skb+0x24/0x1b0 net/core/dev.c:5592
       process_backlog+0x3a0/0x7c0 net/core/dev.c:5920
       __napi_poll+0xb3/0x6e0 net/core/dev.c:6486
       napi_poll net/core/dev.c:6553 [inline]
       net_rx_action+0x9c1/0xd90 net/core/dev.c:6664
       __do_softirq+0x29b/0x9c2 kernel/softirq.c:571
       run_ksoftirqd kernel/softirq.c:934 [inline]
       run_ksoftirqd+0x2d/0x60 kernel/softirq.c:926
       smpboot_thread_fn+0x645/0x9c0 kernel/smpboot.c:164
       kthread+0x2e9/0x3a0 kernel/kthread.c:376
       ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:302

-> #1 (&jsk->sk_session_queue_lock){+.-.}-{2:2}:
       __raw_spin_lock_bh include/linux/spinlock_api_smp.h:126 [inline]
       _raw_spin_lock_bh+0x2f/0x40 kernel/locking/spinlock.c:178
       spin_lock_bh include/linux/spinlock.h:354 [inline]
       j1939_sk_queue_drop_all+0x40/0x2f0 net/can/j1939/socket.c:139
       j1939_sk_netdev_event_netdown+0x7b/0x160 net/can/j1939/socket.c:1272
       j1939_netdev_notify+0x199/0x1d0 net/can/j1939/main.c:372
       notifier_call_chain+0xb5/0x200 kernel/notifier.c:87
       call_netdevice_notifiers_info+0xb5/0x130 net/core/dev.c:1943
       call_netdevice_notifiers_extack net/core/dev.c:1981 [inline]
       call_netdevice_notifiers net/core/dev.c:1995 [inline]
       __dev_notify_flags+0x1da/0x2b0 net/core/dev.c:8571
       dev_change_flags+0x112/0x170 net/core/dev.c:8607
       do_setlink+0x961/0x3bb0 net/core/rtnetlink.c:2780
       __rtnl_newlink+0xd6a/0x17e0 net/core/rtnetlink.c:3546
       rtnl_newlink+0x64/0xa0 net/core/rtnetlink.c:3593
       rtnetlink_rcv_msg+0x43a/0xc90 net/core/rtnetlink.c:6089
       netlink_rcv_skb+0x153/0x420 net/netlink/af_netlink.c:2501
       netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline]
       netlink_unicast+0x543/0x7f0 net/netlink/af_netlink.c:1345
       netlink_sendmsg+0x917/0xe10 net/netlink/af_netlink.c:1921
       sock_sendmsg_nosec net/socket.c:714 [inline]
       sock_sendmsg+0xcf/0x120 net/socket.c:734
       ____sys_sendmsg+0x6eb/0x810 net/socket.c:2492
       ___sys_sendmsg+0xf3/0x170 net/socket.c:2546
       __sys_sendmsg net/socket.c:2575 [inline]
       __do_sys_sendmsg net/socket.c:2584 [inline]
       __se_sys_sendmsg net/socket.c:2582 [inline]
       __x64_sys_sendmsg+0x132/0x220 net/socket.c:2582
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x46/0xb0

-> #0 (&priv->j1939_socks_lock){+.-.}-{2:2}:
       check_prev_add kernel/locking/lockdep.c:3095 [inline]
       check_prevs_add kernel/locking/lockdep.c:3214 [inline]
       validate_chain kernel/locking/lockdep.c:3829 [inline]
       __lock_acquire+0x2abe/0x5660 kernel/locking/lockdep.c:5053
       lock_acquire kernel/locking/lockdep.c:5665 [inline]
       lock_acquire+0x1ab/0x570 kernel/locking/lockdep.c:5630
       __raw_spin_lock_bh include/linux/spinlock_api_smp.h:126 [inline]
       _raw_spin_lock_bh+0x2f/0x40 kernel/locking/spinlock.c:178
       spin_lock_bh include/linux/spinlock.h:354 [inline]
       j1939_sk_errqueue+0x9f/0x1a0 net/can/j1939/socket.c:1078
       __j1939_session_cancel+0x3b9/0x460 net/can/j1939/transport.c:1124
       j1939_tp_rxtimer.cold+0x1f6/0x24f net/can/j1939/transport.c:1249
       __run_hrtimer kernel/time/hrtimer.c:1685 [inline]
       __hrtimer_run_queues+0x609/0xe50 kernel/time/hrtimer.c:1749
       hrtimer_run_softirq+0x17b/0x360 kernel/time/hrtimer.c:1766
       __do_softirq+0x29b/0x9c2 kernel/softirq.c:571
       invoke_softirq kernel/softirq.c:445 [inline]
       __irq_exit_rcu+0x123/0x180 kernel/softirq.c:650
       irq_exit_rcu+0x5/0x20 kernel/softirq.c:662
       sysvec_apic_timer_interrupt+0x93/0xc0 arch/x86/kernel/apic/apic.c:1106
       asm_sysvec_apic_timer_interrupt+0x1b/0x20 arch/x86/include/asm/idtentry.h:649
       native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline]
       arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline]
       acpi_safe_halt drivers/acpi/processor_idle.c:111 [inline]
       acpi_idle_do_entry+0x1c9/0x240 drivers/acpi/processor_idle.c:554
       acpi_idle_enter+0x369/0x510 drivers/acpi/processor_idle.c:691
       cpuidle_enter_state+0x1b1/0xc80 drivers/cpuidle/cpuidle.c:237
       cpuidle_enter+0x4a/0xa0 drivers/cpuidle/cpuidle.c:351
       call_cpuidle kernel/sched/idle.c:155 [inline]
       cpuidle_idle_call kernel/sched/idle.c:236 [inline]
       do_idle+0x3e8/0x590 kernel/sched/idle.c:303
       cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:400
       rest_init+0x169/0x270 init/main.c:726
       arch_call_rest_init+0xf/0x14 init/main.c:882
       start_kernel+0x46e/0x48f init/main.c:1137
       secondary_startup_64_no_verify+0xce/0xdb

other info that might help us debug this:

Chain exists of:
  &priv->j1939_socks_lock --> &jsk->sk_session_queue_lock --> &priv->active_session_list_lock

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&priv->active_session_list_lock);
                               lock(&jsk->sk_session_queue_lock);
                               lock(&priv->active_session_list_lock);
  lock(&priv->j1939_socks_lock);

 *** DEADLOCK ***

1 lock held by swapper/0/0:
 #0: ffff888077729088 (&priv->active_session_list_lock){+.-.}-{2:2}, at: spin_lock_bh include/linux/spinlock.h:354 [inline]
 #0: ffff888077729088 (&priv->active_session_list_lock){+.-.}-{2:2}, at: j1939_session_list_lock net/can/j1939/transport.c:238 [inline]
 #0: ffff888077729088 (&priv->active_session_list_lock){+.-.}-{2:2}, at: j1939_tp_rxtimer+0xe5/0x220 net/can/j1939/transport.c:1240

stack backtrace:
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.19.0-rc2-syzkaller-00049-g24625f7d91fb #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 <IRQ>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
 check_noncircular+0x25f/0x2e0 kernel/locking/lockdep.c:2175
 check_prev_add kernel/locking/lockdep.c:3095 [inline]
 check_prevs_add kernel/locking/lockdep.c:3214 [inline]
 validate_chain kernel/locking/lockdep.c:3829 [inline]
 __lock_acquire+0x2abe/0x5660 kernel/locking/lockdep.c:5053
 lock_acquire kernel/locking/lockdep.c:5665 [inline]
 lock_acquire+0x1ab/0x570 kernel/locking/lockdep.c:5630
 __raw_spin_lock_bh include/linux/spinlock_api_smp.h:126 [inline]
 _raw_spin_lock_bh+0x2f/0x40 kernel/locking/spinlock.c:178
 spin_lock_bh include/linux/spinlock.h:354 [inline]
 j1939_sk_errqueue+0x9f/0x1a0 net/can/j1939/socket.c:1078
 __j1939_session_cancel+0x3b9/0x460 net/can/j1939/transport.c:1124
 j1939_tp_rxtimer.cold+0x1f6/0x24f net/can/j1939/transport.c:1249
 __run_hrtimer kernel/time/hrtimer.c:1685 [inline]
 __hrtimer_run_queues+0x609/0xe50 kernel/time/hrtimer.c:1749
 hrtimer_run_softirq+0x17b/0x360 kernel/time/hrtimer.c:1766
 __do_softirq+0x29b/0x9c2 kernel/softirq.c:571
 invoke_softirq kernel/softirq.c:445 [inline]
 __irq_exit_rcu+0x123/0x180 kernel/softirq.c:650
 irq_exit_rcu+0x5/0x20 kernel/softirq.c:662
 sysvec_apic_timer_interrupt+0x93/0xc0 arch/x86/kernel/apic/apic.c:1106
 </IRQ>
 <TASK>
 asm_sysvec_apic_timer_interrupt+0x1b/0x20 arch/x86/include/asm/idtentry.h:649
RIP: 0010:native_save_fl arch/x86/include/asm/irqflags.h:29 [inline]
RIP: 0010:arch_local_save_flags arch/x86/include/asm/irqflags.h:70 [inline]
RIP: 0010:arch_irqs_disabled arch/x86/include/asm/irqflags.h:130 [inline]
RIP: 0010:acpi_safe_halt drivers/acpi/processor_idle.c:112 [inline]
RIP: 0010:acpi_idle_do_entry+0x1c9/0x240 drivers/acpi/processor_idle.c:554
Code: 89 de e8 4a 53 00 f8 84 db 75 98 e8 41 57 00 f8 e8 2c a7 06 f8 66 90 e8 35 57 00 f8 0f 00 2d 2e f0 b9 00 e8 29 57 00 f8 fb f4 <9c> 5b 81 e3 00 02 00 00 fa 31 ff 48 89 de e8 74 53 00 f8 48 85 db
RSP: 0018:ffffffff8ba07d38 EFLAGS: 00000293
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: ffffffff8babc940 RSI: ffffffff897a1ad7 RDI: 0000000000000000
RBP: ffff888017071064 R08: 0000000000000001 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000001
R13: ffff888017071000 R14: ffff888017071064 R15: ffff88801b1cd804
 acpi_idle_enter+0x369/0x510 drivers/acpi/processor_idle.c:691
 cpuidle_enter_state+0x1b1/0xc80 drivers/cpuidle/cpuidle.c:237
 cpuidle_enter+0x4a/0xa0 drivers/cpuidle/cpuidle.c:351
 call_cpuidle kernel/sched/idle.c:155 [inline]
 cpuidle_idle_call kernel/sched/idle.c:236 [inline]
 do_idle+0x3e8/0x590 kernel/sched/idle.c:303
 cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:400
 rest_init+0x169/0x270 init/main.c:726
 arch_call_rest_init+0xf/0x14 init/main.c:882
 start_kernel+0x46e/0x48f init/main.c:1137
 secondary_startup_64_no_verify+0xce/0xdb
 </TASK>
vcan0: j1939_xtp_rx_abort_one: 0xffff88814717a000: 0x00000: (3) A timeout occurred and this is the connection abort to close the session.
vcan0: j1939_xtp_rx_abort_one: 0xffff88807b7b3800: 0x00000: (3) A timeout occurred and this is the connection abort to close the session.
----------------
Code disassembly (best guess):
   0:	89 de                	mov    %ebx,%esi
   2:	e8 4a 53 00 f8       	callq  0xf8005351
   7:	84 db                	test   %bl,%bl
   9:	75 98                	jne    0xffffffa3
   b:	e8 41 57 00 f8       	callq  0xf8005751
  10:	e8 2c a7 06 f8       	callq  0xf806a741
  15:	66 90                	xchg   %ax,%ax
  17:	e8 35 57 00 f8       	callq  0xf8005751
  1c:	0f 00 2d 2e f0 b9 00 	verw   0xb9f02e(%rip)        # 0xb9f051
  23:	e8 29 57 00 f8       	callq  0xf8005751
  28:	fb                   	sti
  29:	f4                   	hlt
* 2a:	9c                   	pushfq <-- trapping instruction
  2b:	5b                   	pop    %rbx
  2c:	81 e3 00 02 00 00    	and    $0x200,%ebx
  32:	fa                   	cli
  33:	31 ff                	xor    %edi,%edi
  35:	48 89 de             	mov    %rbx,%rsi
  38:	e8 74 53 00 f8       	callq  0xf80053b1
  3d:	48 85 db             	test   %rbx,%rbx

Crashes (227):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/06/14 22:53 upstream 24625f7d91fb 127d1faf .config strace log report syz C ci-upstream-kasan-gce possible deadlock in j1939_sk_errqueue
2023/03/28 22:48 upstream fcd476ea6a88 48c74771 .config console log report info ci-upstream-kasan-gce possible deadlock in j1939_sk_errqueue
2023/03/26 06:13 upstream 4bdec23f971b fbf0499a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in j1939_sk_errqueue
2023/03/20 22:42 upstream 7d31677bb7b1 7939252e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in j1939_sk_errqueue
2023/03/13 08:44 upstream eeac8ede1755 5205ef30 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in j1939_sk_errqueue
2023/03/05 15:16 upstream b01fe98d34f3 f8902b57 .config console log report info ci-qemu-upstream possible deadlock in j1939_sk_errqueue
2023/03/04 21:58 upstream 0988a0ea7919 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in j1939_sk_errqueue
2023/03/04 05:27 upstream 0a3f9a6b0265 f8902b57 .config console log report info ci-upstream-kasan-gce-root possible deadlock in j1939_sk_errqueue
2023/02/25 00:16 upstream a93e884edf61 ee50e71c .config console log report info ci-upstream-kasan-gce possible deadlock in j1939_sk_errqueue
2023/02/13 02:00 upstream ceaa837f96ad 93e26d60 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in j1939_sk_errqueue
2023/02/06 09:41 upstream d2d11f342b17 be607b78 .config console log report info ci-upstream-kasan-gce possible deadlock in j1939_sk_errqueue
2023/01/28 03:58 upstream 83abd4d4c4be 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in j1939_sk_errqueue
2023/01/27 00:27 upstream 7c46948a6e9c 9dfcf09c .config console log report info ci-upstream-kasan-gce possible deadlock in j1939_sk_errqueue
2023/01/14 22:06 upstream 97ec4d559d93 a63719e7 .config console log report info ci-upstream-kasan-gce-smack-root possible deadlock in j1939_sk_errqueue
2023/01/03 12:42 upstream 69b41ac87e4a ab32d508 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in j1939_sk_errqueue
2022/12/28 17:40 upstream 1b929c02afd3 44712fbc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce possible deadlock in j1939_sk_errqueue
2022/12/23 04:36 upstream 8395ae05cb5a 9da18ae8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in j1939_sk_errqueue
2022/12/21 04:12 upstream b6bb9676f216 d3e76707 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in j1939_sk_errqueue
2022/11/29 14:45 upstream ca57f02295f1 05dc7993 .config console log report info ci-upstream-kasan-gce possible deadlock in j1939_sk_errqueue
2022/11/29 12:22 upstream ca57f02295f1 05dc7993 .config console log report info ci-upstream-kasan-gce possible deadlock in j1939_sk_errqueue
2022/09/03 20:29 upstream 42cf58c272ee 28811d0a .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce-smack-root possible deadlock in j1939_sk_errqueue
2022/08/27 02:38 upstream 3e5c673f0d75 07177916 .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in j1939_sk_errqueue
2022/08/11 08:03 upstream 200e340f2196 a6201f11 .config console log report info ci-upstream-kasan-gce possible deadlock in j1939_sk_errqueue
2022/07/12 20:10 upstream 72a8e05d4f66 d91dd8ea .config console log report info ci-upstream-kasan-gce-root possible deadlock in j1939_sk_errqueue
2022/07/11 13:34 upstream 32346491ddf2 da3d6955 .config console log report info ci-upstream-kasan-gce possible deadlock in j1939_sk_errqueue
2022/07/04 22:51 upstream c1084b6c5620 bff65f44 .config console log report info ci-upstream-kasan-gce possible deadlock in j1939_sk_errqueue
2022/07/04 12:41 upstream 88084a3df167 bff65f44 .config console log report info ci-upstream-kasan-gce possible deadlock in j1939_sk_errqueue
2022/07/03 10:56 upstream 34074da5424c 1434eec0 .config console log report info ci-upstream-kasan-gce possible deadlock in j1939_sk_errqueue
2022/06/27 00:42 upstream 893d1eaa56e8 a371c43c .config console log report info ci-upstream-kasan-gce-root possible deadlock in j1939_sk_errqueue
2023/03/29 02:12 upstream fcd476ea6a88 fc067f05 .config console log report info ci-upstream-kasan-gce-386 possible deadlock in j1939_sk_errqueue
2023/03/22 04:35 upstream 2faac9a98f01 8b4eb097 .config console log report info ci-qemu-upstream-386 possible deadlock in j1939_sk_errqueue
2023/03/17 13:19 upstream 38e04b3e4240 18b58603 .config console log report info ci-upstream-kasan-gce-386 possible deadlock in j1939_sk_errqueue
2023/03/04 16:35 upstream 0988a0ea7919 f8902b57 .config console log report info ci-upstream-kasan-gce-386 possible deadlock in j1939_sk_errqueue
2023/01/15 08:02 upstream 7c6984405241 a63719e7 .config console log report info ci-upstream-kasan-gce-386 possible deadlock in j1939_sk_errqueue
2022/12/22 17:02 upstream 9d2f6060fe4c c692fab1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 possible deadlock in j1939_sk_errqueue
2022/11/16 21:06 upstream 59d0d52c30d4 3a127a31 .config console log report info ci-upstream-kasan-gce-386 possible deadlock in j1939_sk_errqueue
2022/10/08 06:57 upstream 4c86114194e6 0de35f24 .config console log report info ci-upstream-kasan-gce-386 possible deadlock in j1939_sk_errqueue
2022/08/24 06:35 upstream df0219d11b6f cea8b0f7 .config console log report info ci-upstream-kasan-gce-386 possible deadlock in j1939_sk_errqueue
2022/08/21 11:48 upstream 15b3f48a4339 26a13b38 .config console log report info ci-qemu-upstream-386 possible deadlock in j1939_sk_errqueue
2022/08/15 17:56 upstream 7ebfc85e2cd7 8dfcaa3d .config console log report info ci-upstream-kasan-gce-386 possible deadlock in j1939_sk_errqueue
2022/07/21 11:28 upstream 353f7988dd84 6e67af9d .config console log report info ci-upstream-kasan-gce-386 possible deadlock in j1939_sk_errqueue
2022/07/11 03:08 upstream 5867f3b88bb5 b5765a15 .config console log report info ci-upstream-kasan-gce-386 possible deadlock in j1939_sk_errqueue
2022/06/25 05:11 upstream 6a0a17e6c6d1 a371c43c .config console log report info ci-upstream-kasan-gce-386 possible deadlock in j1939_sk_errqueue
2022/10/04 12:17 net-old 93e2be344a7d 77d3f689 .config console log report info [disk image] [vmlinux] ci-upstream-net-this-kasan-gce possible deadlock in j1939_sk_errqueue
2022/09/10 22:25 net-old 64ae13ed4784 356d8217 .config console log report info [disk image] [vmlinux] ci-upstream-net-this-kasan-gce possible deadlock in j1939_sk_errqueue
2021/10/04 03:33 net-old 7cd8b1542a7b db0f5787 .config console log report info ci-upstream-net-this-kasan-gce possible deadlock in j1939_sk_errqueue
2023/02/02 06:14 net-next-old dd25cfab16e6 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in j1939_sk_errqueue
2022/12/27 19:00 net-next-old c183e6c3ec34 44712fbc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in j1939_sk_errqueue
2022/12/15 23:45 net-next-old 7e68dd7d07a2 6f9c033e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in j1939_sk_errqueue
2022/12/08 21:46 net-next-old d8b879c00f69 1034e5fa .config console log report info ci-upstream-net-kasan-gce possible deadlock in j1939_sk_errqueue
2022/11/04 06:08 net-next-old fbeb229a6622 6d752409 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in j1939_sk_errqueue
2022/08/31 13:01 net-next-old 146ecbac1d32 51e54e30 .config console log report info ci-upstream-net-kasan-gce possible deadlock in j1939_sk_errqueue
2023/01/13 14:59 linux-next 0a093b2893c7 529798b0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in j1939_sk_errqueue
2023/01/07 15:28 linux-next cc3c08b41a9c 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in j1939_sk_errqueue
2023/01/10 00:29 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 358a161a6a9e 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in j1939_sk_errqueue
2022/10/21 04:01 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci bbed346d5a96 a0fd4dab .config console log report info ci-upstream-gce-arm64 possible deadlock in j1939_sk_errqueue
2022/10/06 04:07 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci bbed346d5a96 2c6543ad .config console log report info [disk image] [vmlinux] ci-upstream-gce-arm64 possible deadlock in j1939_sk_errqueue
2022/09/26 08:19 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci c194837ebb57 d59ba983 .config console log report info [disk image] [vmlinux] ci-upstream-gce-arm64 possible deadlock in j1939_sk_errqueue
2022/09/21 23:30 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci aa49f95768a9 60af5050 .config console log report info [disk image] [vmlinux] ci-upstream-gce-arm64 possible deadlock in j1939_sk_errqueue
2022/09/17 20:09 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a6b443748715 dd9a85ff .config console log report info [disk image] [vmlinux] ci-upstream-gce-arm64 possible deadlock in j1939_sk_errqueue
* Struck through repros no longer work on HEAD.