syzbot


possible deadlock in rds_tcp_reset_callbacks

Status: upstream: reported C repro on 2020/02/20 02:21
Reported-by: syzbot+574ab7872249eb9cf9b6@syzkaller.appspotmail.com
First crash: 1586d, last: 492d
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in rds_tcp_reset_callbacks rds C error 1458 595d 673d 22/27 fixed on 2023/02/24 13:50
Fix bisection attempts (2)
Created Duration User Patch Repo Result
2023/02/18 11:43 25m bisect fix linux-4.14.y job log (0) log
2023/01/19 10:59 24m bisect fix linux-4.14.y job log (0) log

Sample crash report:
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_macvtap: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth0_macvtap: link becomes ready
device veth0_vlan entered promiscuous mode
device veth1_vlan entered promiscuous mode
======================================================
WARNING: possible circular locking dependency detected
4.14.289-syzkaller #0 Not tainted
------------------------------------------------------
kworker/u4:2/34 is trying to acquire lock:
IPv6: ADDRCONF(NETDEV_UP): macvlan0: link is not ready
 ((&(&cp->cp_send_w)->work)){+.+.}, at: [<ffffffff81367998>] flush_work+0x88/0x770 kernel/workqueue.c:2887

but task is already holding lock:
IPv6: ADDRCONF(NETDEV_CHANGE): macvlan0: link becomes ready
 (k-sk_lock-AF_INET){+.+.}, at: [<ffffffff869c23f1>] lock_sock include/net/sock.h:1473 [inline]
 (k-sk_lock-AF_INET){+.+.}, at: [<ffffffff869c23f1>] rds_tcp_reset_callbacks+0x181/0x450 net/rds/tcp.c:165

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (k-sk_lock-AF_INET){+.+.}:
       lock_sock_nested+0xb7/0x100 net/core/sock.c:2813
       lock_sock include/net/sock.h:1473 [inline]
       do_tcp_setsockopt.constprop.0+0xfb/0x1c10 net/ipv4/tcp.c:2564
       tcp_setsockopt net/ipv4/tcp.c:2832 [inline]
       tcp_setsockopt+0xa7/0xc0 net/ipv4/tcp.c:2824
       kernel_setsockopt+0xfb/0x1b0 net/socket.c:3396
       rds_tcp_cork net/rds/tcp_send.c:43 [inline]
       rds_tcp_xmit_path_prepare+0xaf/0xe0 net/rds/tcp_send.c:50
       rds_send_xmit+0x1ae/0x1c00 net/rds/send.c:187
       rds_send_worker+0x6d/0x240 net/rds/threads.c:189
       process_one_work+0x793/0x14a0 kernel/workqueue.c:2117
       worker_thread+0x5cc/0xff0 kernel/workqueue.c:2251
       kthread+0x30d/0x420 kernel/kthread.c:232
       ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404

-> #0 ((&(&cp->cp_send_w)->work)){+.+.}:
       lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
       flush_work+0xad/0x770 kernel/workqueue.c:2890
IPv6: ADDRCONF(NETDEV_CHANGE): vlan0: link becomes ready
       __cancel_work_timer+0x321/0x460 kernel/workqueue.c:2965
       rds_tcp_reset_callbacks+0x18d/0x450 net/rds/tcp.c:167
       rds_tcp_accept_one+0x61a/0x8b0 net/rds/tcp_listen.c:194
       rds_tcp_accept_worker+0x4d/0x70 net/rds/tcp.c:407
       process_one_work+0x793/0x14a0 kernel/workqueue.c:2117
       worker_thread+0x5cc/0xff0 kernel/workqueue.c:2251
       kthread+0x30d/0x420 kernel/kthread.c:232
IPv6: ADDRCONF(NETDEV_CHANGE): vlan1: link becomes ready
       ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(k-sk_lock-AF_INET);
                               lock((&(&cp->cp_send_w)->work));
                               lock(k-sk_lock-AF_INET);
  lock((&(&cp->cp_send_w)->work));

 *** DEADLOCK ***

4 locks held by kworker/u4:2/34:
 #0:  ("%s""krdsd"){+.+.}, at: [<ffffffff81364eb0>] process_one_work+0x6b0/0x14a0 kernel/workqueue.c:2088
 #1:  ((&rtn->rds_tcp_accept_w)){+.+.}, at: [<ffffffff81364ee6>] process_one_work+0x6e6/0x14a0 kernel/workqueue.c:2092
 #2:  (&tc->t_conn_path_lock){+.+.}, at: [<ffffffff869c41e2>] rds_tcp_accept_one+0x502/0x8b0 net/rds/tcp_listen.c:186
 #3:  (k-sk_lock-AF_INET){+.+.}, at: [<ffffffff869c23f1>] lock_sock include/net/sock.h:1473 [inline]
 #3:  (k-sk_lock-AF_INET){+.+.}, at: [<ffffffff869c23f1>] rds_tcp_reset_callbacks+0x181/0x450 net/rds/tcp.c:165

stack backtrace:
CPU: 1 PID: 34 Comm: kworker/u4:2 Not tainted 4.14.289-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/29/2022
Workqueue: krdsd rds_tcp_accept_worker
Call Trace:
 __dump_stack lib/dump_stack.c:17 [inline]
 dump_stack+0x1b2/0x281 lib/dump_stack.c:58
 print_circular_bug.constprop.0.cold+0x2d7/0x41e kernel/locking/lockdep.c:1258
 check_prev_add kernel/locking/lockdep.c:1905 [inline]
 check_prevs_add kernel/locking/lockdep.c:2022 [inline]
 validate_chain kernel/locking/lockdep.c:2464 [inline]
 __lock_acquire+0x2e0e/0x3f20 kernel/locking/lockdep.c:3491
 lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
 flush_work+0xad/0x770 kernel/workqueue.c:2890
 __cancel_work_timer+0x321/0x460 kernel/workqueue.c:2965
 rds_tcp_reset_callbacks+0x18d/0x450 net/rds/tcp.c:167
 rds_tcp_accept_one+0x61a/0x8b0 net/rds/tcp_listen.c:194
 rds_tcp_accept_worker+0x4d/0x70 net/rds/tcp.c:407
 process_one_work+0x793/0x14a0 kernel/workqueue.c:2117
 worker_thread+0x5cc/0xff0 kernel/workqueue.c:2251
 kthread+0x30d/0x420 kernel/kthread.c:232
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
device veth1_vlan entered promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): macvlan0: link is not ready
device veth0_macvtap entered promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): macvtap0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): macvlan1: link is not ready
IPv6: ADDRCONF(NETDEV_UP): macvlan1: link is not ready
IPv6: ADDRCONF(NETDEV_UP): veth0_macvtap: link is not ready
device veth1_macvtap entered promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): macsec0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): veth1_macvtap: link is not ready
IPv6: ADDRCONF(NETDEV_UP): veth0_macvtap: link is not ready
IPv6: ADDRCONF(NETDEV_CHANGE): macvlan1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): macvlan0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): macvlan1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): macvtap0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): macsec0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_macvtap: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth0_macvtap: link becomes ready
IPv6: ADDRCONF(NETDEV_UP): veth0_to_batadv: link is not ready
IPv6: ADDRCONF(NETDEV_UP): veth1_to_batadv: link is not ready
device veth0_macvtap entered promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): macvtap0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): veth1_macvtap: link is not ready
IPv6: ADDRCONF(NETDEV_CHANGE): macvtap0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_macvtap: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth0_macvtap: link becomes ready
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
IPv6: ADDRCONF(NETDEV_UP): batadv_slave_0: link is not ready
batman_adv: batadv0: Interface activated: batadv_slave_0
device veth1_macvtap entered promiscuous mode
device veth0_macvtap entered promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): macvtap0: link is not ready
IPv6: ADDRCONF(NETDEV_CHANGE): macvtap0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): batadv_slave_0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth0_to_batadv: link becomes ready
IPv6: ADDRCONF(NETDEV_UP): veth0_to_batadv: link is not ready
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_1
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_1
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_1
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
IPv6: ADDRCONF(NETDEV_UP): batadv_slave_1: link is not ready
batman_adv: batadv0: Interface activated: batadv_slave_1
device veth1_macvtap entered promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): veth1_to_batadv: link is not ready
IPv6: ADDRCONF(NETDEV_CHANGE): batadv_slave_1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_batadv: link becomes ready
IPv6: ADDRCONF(NETDEV_UP): veth0_to_batadv: link is not ready
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
IPv6: ADDRCONF(NETDEV_UP): batadv_slave_0: link is not ready
batman_adv: batadv0: Interface activated: batadv_slave_0
IPv6: ADDRCONF(NETDEV_UP): veth1_to_batadv: link is not ready
IPv6: ADDRCONF(NETDEV_CHANGE): batadv_slave_0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth0_to_batadv: link becomes ready
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_1
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_1
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_1
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_1
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
IPv6: ADDRCONF(NETDEV_UP): batadv_slave_1: link is not ready
batman_adv: batadv0: Interface activated: batadv_slave_1
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3d) already exists on: batadv_slave_0
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
IPv6: ADDRCONF(NETDEV_UP): batadv_slave_0: link is not ready
batman_adv: batadv0: Interface activated: batadv_slave_0
IPv6: ADDRCONF(NETDEV_CHANGE): batadv_slave_1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_batadv: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): batadv_slave_0: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth0_to_batadv: link becomes ready
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_1
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_1
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_1
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_1
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
batman_adv: The newly added mac address (aa:aa:aa:aa:aa:3e) already exists on: batadv_slave_1
batman_adv: It is strongly recommended to keep mac addresses unique to avoid problems!
IPv6: ADDRCONF(NETDEV_UP): batadv_slave_1: link is not ready
batman_adv: batadv0: Interface activated: batadv_slave_1
IPv6: ADDRCONF(NETDEV_CHANGE): batadv_slave_1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_batadv: link becomes ready

Crashes (5140):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/07/24 07:17 linux-4.14.y 9c3bf9cf362f 22343af4 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/07/14 10:55 linux-4.14.y 424a46ea058e 5d921b08 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/07/14 01:04 linux-4.14.y 424a46ea058e 5d921b08 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/07/11 05:29 linux-4.14.y 1048779a1d7d b5765a15 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/07/10 07:10 linux-4.14.y 1048779a1d7d b5765a15 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/07/10 03:41 linux-4.14.y 1048779a1d7d b5765a15 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/07/09 09:06 linux-4.14.y 1048779a1d7d b5765a15 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/07/05 21:15 linux-4.14.y ed2e96e11936 bff65f44 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/07/03 00:44 linux-4.14.y ed2e96e11936 1434eec0 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/07/01 09:07 linux-4.14.y f051383ef03b 1434eec0 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/30 16:07 linux-4.14.y f051383ef03b 1434eec0 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/29 21:20 linux-4.14.y f051383ef03b 1434eec0 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/27 16:17 linux-4.14.y f051383ef03b a371c43c .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/25 17:37 linux-4.14.y f051383ef03b a371c43c .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/23 02:42 linux-4.14.y 84bae26850e3 912f5df7 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/22 23:23 linux-4.14.y 84bae26850e3 912f5df7 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/22 12:59 linux-4.14.y 84bae26850e3 0fc5c330 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/20 09:32 linux-4.14.y 84bae26850e3 8f633d84 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/20 07:13 linux-4.14.y 84bae26850e3 8f633d84 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/20 06:38 linux-4.14.y 84bae26850e3 8f633d84 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/20 02:00 linux-4.14.y 84bae26850e3 8f633d84 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/19 09:19 linux-4.14.y 84bae26850e3 8f633d84 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/19 08:54 linux-4.14.y 84bae26850e3 8f633d84 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/19 07:15 linux-4.14.y 84bae26850e3 8f633d84 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/18 19:11 linux-4.14.y 84bae26850e3 8f633d84 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/14 05:14 linux-4.14.y b8f3be299d51 0f087040 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/13 14:41 linux-4.14.y b8f3be299d51 0d5abf15 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/13 06:07 linux-4.14.y b8f3be299d51 0d5abf15 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/12 11:32 linux-4.14.y b8f3be299d51 0d5abf15 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/12 10:57 linux-4.14.y b8f3be299d51 0d5abf15 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/12 03:54 linux-4.14.y b8f3be299d51 0d5abf15 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/11 17:41 linux-4.14.y b8f3be299d51 0d5abf15 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/11 14:51 linux-4.14.y b8f3be299d51 0d5abf15 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/11 13:38 linux-4.14.y b8f3be299d51 0d5abf15 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/10 07:50 linux-4.14.y b8f3be299d51 0d5abf15 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/10 01:29 linux-4.14.y b8f3be299d51 0d5abf15 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/09 19:54 linux-4.14.y b8f3be299d51 0d5abf15 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/09 12:00 linux-4.14.y b8f3be299d51 0d5abf15 .config console log report syz C ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2020/02/21 21:03 linux-4.14.y 98db2bf27b9e 2ffa6679 .config console log report syz C ci2-linux-4-14
2022/07/01 03:04 linux-4.14.y f051383ef03b 1434eec0 .config console log report syz ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/06/24 18:55 linux-4.14.y 84bae26850e3 a371c43c .config console log report syz ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2020/02/20 03:37 linux-4.14.y 98db2bf27b9e b690a6e3 .config console log report syz ci2-linux-4-14
2022/10/26 00:45 linux-4.14.y 9d5c0b3a8e1a 2159e4d2 .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/10/22 07:57 linux-4.14.y 9d5c0b3a8e1a c0b80a55 .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/10/21 10:59 linux-4.14.y 9d5c0b3a8e1a 63e790dd .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/10/20 22:41 linux-4.14.y 9d5c0b3a8e1a a0fd4dab .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/10/18 11:08 linux-4.14.y 9d5c0b3a8e1a b31320fc .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/10/15 14:58 linux-4.14.y 9d5c0b3a8e1a 67cb024c .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/10/10 18:59 linux-4.14.y 9d5c0b3a8e1a 5bcf0c31 .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/09/22 16:56 linux-4.14.y 4edbf74132a4 0042f2b4 .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/09/12 16:39 linux-4.14.y 65640c873dcf f371ed7e .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/09/11 17:05 linux-4.14.y 65640c873dcf 356d8217 .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/09/10 08:09 linux-4.14.y 65640c873dcf 356d8217 .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/09/09 23:36 linux-4.14.y 65640c873dcf 356d8217 .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/09/09 17:22 linux-4.14.y 65640c873dcf 90058bdc .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/09/08 11:38 linux-4.14.y 65640c873dcf f3027468 .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/09/08 01:45 linux-4.14.y 65640c873dcf 435aeef7 .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/09/08 00:05 linux-4.14.y 65640c873dcf 435aeef7 .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/09/07 12:21 linux-4.14.y 65640c873dcf c5b7bc57 .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/09/07 00:32 linux-4.14.y 65640c873dcf 5fc30c37 .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/09/06 23:19 linux-4.14.y 65640c873dcf 5fc30c37 .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/09/06 10:53 linux-4.14.y 65640c873dcf 65aea2b9 .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/09/05 11:05 linux-4.14.y 65640c873dcf 922294ab .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/09/03 15:19 linux-4.14.y e548869f356f 28811d0a .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/09/03 03:34 linux-4.14.y e548869f356f 49e94a20 .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/09/02 14:22 linux-4.14.y e548869f356f 25194605 .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/09/02 05:05 linux-4.14.y e548869f356f a805568e .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/09/02 02:26 linux-4.14.y e548869f356f a805568e .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/09/01 03:18 linux-4.14.y e548869f356f b01ec571 .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/08/31 12:10 linux-4.14.y e548869f356f 51e54e30 .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/08/31 09:57 linux-4.14.y e548869f356f 51e54e30 .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/08/30 15:48 linux-4.14.y e548869f356f 4a380809 .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/08/30 05:06 linux-4.14.y e548869f356f 4a380809 .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/08/29 16:10 linux-4.14.y e548869f356f d7593c58 .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/08/29 11:28 linux-4.14.y e548869f356f 94da0b6b .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/08/27 06:31 linux-4.14.y e548869f356f 07177916 .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/08/27 03:39 linux-4.14.y e548869f356f 07177916 .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/08/27 01:46 linux-4.14.y e548869f356f 07177916 .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/08/27 00:45 linux-4.14.y e548869f356f 07177916 .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/08/26 18:16 linux-4.14.y e548869f356f e5a303f1 .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/08/26 13:03 linux-4.14.y e548869f356f e5a303f1 .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/08/25 10:26 linux-4.14.y e548869f356f 514514f6 .config console log report info [disk image] [vmlinux] ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/08/24 10:38 linux-4.14.y b641242202ed 514514f6 .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/08/20 07:56 linux-4.14.y b641242202ed 26a13b38 .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/08/19 23:32 linux-4.14.y b641242202ed 26a13b38 .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/08/18 23:12 linux-4.14.y b641242202ed 26a13b38 .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/08/18 10:25 linux-4.14.y b641242202ed d58e263f .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/08/17 22:14 linux-4.14.y b641242202ed a9409d47 .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/08/17 07:59 linux-4.14.y b641242202ed 4e72d229 .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/08/16 21:01 linux-4.14.y b641242202ed 9e4b39c2 .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/08/12 13:23 linux-4.14.y b641242202ed 402cd70d .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/08/12 05:10 linux-4.14.y b641242202ed 21724cb2 .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2022/08/11 22:34 linux-4.14.y b641242202ed 21724cb2 .config console log report info ci2-linux-4-14 possible deadlock in rds_tcp_reset_callbacks
2021/01/17 14:00 linux-4.14.y 2762b48e9611 813be542 .config console log report info ci2-linux-4-14
2020/02/20 02:20 linux-4.14.y 98db2bf27b9e b690a6e3 .config console log report ci2-linux-4-14
* Struck through repros no longer work on HEAD.