syzbot


possible deadlock in sco_conn_del

Status: fixed on 2023/07/01 16:05
Subsystems: bluetooth
[Documentation on labels]
Reported-by: syzbot+b825d87fe2d043e3e652@syzkaller.appspotmail.com
Fix commit: a2ac591cb4d8 Bluetooth: Fix UAF in hci_conn_hash_flush again
First crash: 806d, last: 399d
Cause bisection: introduced by (bisect log) :
commit 92b8aa6d18f7a9ae36a0f71d31742aeef201207a
Author: Ying Hsu <yinghsu@chromium.org>
Date: Sat Mar 26 07:09:28 2022 +0000

  Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout

Crash: possible deadlock in sco_conn_del (log)
Repro: C syz .config
  
Fix bisection: fixed by (bisect log) :
commit a2ac591cb4d83e1f2d4b4adb3c14b2c79764650a
Author: Ruihan Li <lrh2000@pku.edu.cn>
Date: Wed May 3 13:39:36 2023 +0000

  Bluetooth: Fix UAF in hci_conn_hash_flush again

  
Discussions (2)
Title Replies (including bot) Last reply
[syzbot] possible deadlock in sco_conn_del 1 (5) 2023/06/19 06:10
[syzbot] Monthly bluetooth report 0 (1) 2023/03/29 10:03
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 possible deadlock in sco_conn_del origin:lts-only C done 217 1d13h 462d 0/3 upstream: reported C repro on 2023/03/13 19:51
linux-5.15 possible deadlock in sco_conn_del missing-backport origin:lts-only C inconclusive 225 1d16h 461d 0/3 upstream: reported C repro on 2023/03/14 20:00
Last patch testing requests (2)
Created Duration User Patch Repo Result
2022/04/12 01:54 11m hdanton@sina.com patch https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/ d12d7e1cfe38 OK
2022/04/11 23:27 8m hdanton@sina.com patch https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/ d12d7e1cfe38 report log
Fix bisection attempts (2)
Created Duration User Patch Repo Result
2023/06/16 11:02 4h06m bisect fix upstream job log (1)
2023/05/16 06:14 54m bisect fix upstream job log (0) log

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
6.2.0-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor373/5099 is trying to acquire lock:
ffff88802c088130 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1725 [inline]
ffff88802c088130 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}, at: sco_conn_del+0x12c/0x2b0 net/bluetooth/sco.c:197

but task is already holding lock:
ffffffff8e2ff068 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1790 [inline]
ffffffff8e2ff068 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xd9/0x260 net/bluetooth/hci_conn.c:2437

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (hci_cb_list_lock){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x12f/0x1360 kernel/locking/mutex.c:747
       hci_connect_cfm include/net/bluetooth/hci_core.h:1775 [inline]
       hci_remote_features_evt+0x49e/0xa20 net/bluetooth/hci_event.c:3768
       hci_event_func net/bluetooth/hci_event.c:7485 [inline]
       hci_event_packet+0x956/0xfd0 net/bluetooth/hci_event.c:7537
       hci_rx_work+0xaeb/0x1230 net/bluetooth/hci_core.c:4043
       process_one_work+0x9bf/0x1710 kernel/workqueue.c:2289
       worker_thread+0x669/0x1090 kernel/workqueue.c:2436
       kthread+0x2e8/0x3a0 kernel/kthread.c:376
       ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308

-> #1 (&hdev->lock){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x12f/0x1360 kernel/locking/mutex.c:747
       sco_sock_connect+0x1ea/0xa60 net/bluetooth/sco.c:593
       __sys_connect_file+0x153/0x1a0 net/socket.c:1979
       __sys_connect+0x165/0x1a0 net/socket.c:1996
       __do_sys_connect net/socket.c:2006 [inline]
       __se_sys_connect net/socket.c:2003 [inline]
       __x64_sys_connect+0x73/0xb0 net/socket.c:2003
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #0 (sk_lock-AF_BLUETOOTH-BTPROTO_SCO){+.+.}-{0:0}:
       check_prev_add kernel/locking/lockdep.c:3097 [inline]
       check_prevs_add kernel/locking/lockdep.c:3216 [inline]
       validate_chain kernel/locking/lockdep.c:3831 [inline]
       __lock_acquire+0x2a43/0x56d0 kernel/locking/lockdep.c:5055
       lock_acquire kernel/locking/lockdep.c:5668 [inline]
       lock_acquire+0x1e3/0x630 kernel/locking/lockdep.c:5633
       lock_sock_nested+0x3a/0xf0 net/core/sock.c:3471
       lock_sock include/net/sock.h:1725 [inline]
       sco_conn_del+0x12c/0x2b0 net/bluetooth/sco.c:197
       sco_disconn_cfm+0x75/0xb0 net/bluetooth/sco.c:1379
       hci_disconn_cfm include/net/bluetooth/hci_core.h:1793 [inline]
       hci_conn_hash_flush+0x126/0x260 net/bluetooth/hci_conn.c:2437
       hci_dev_close_sync+0x5fb/0x1200 net/bluetooth/hci_sync.c:4850
       hci_dev_do_close+0x31/0x70 net/bluetooth/hci_core.c:554
       hci_rfkill_set_block+0x161/0x1d0 net/bluetooth/hci_core.c:956
       rfkill_set_block+0x1f9/0x540 net/rfkill/core.c:345
       rfkill_fop_write+0x2c7/0x570 net/rfkill/core.c:1286
       vfs_write+0x2db/0xdd0 fs/read_write.c:582
       ksys_write+0x1ec/0x250 fs/read_write.c:637
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

other info that might help us debug this:

Chain exists of:
  sk_lock-AF_BLUETOOTH-BTPROTO_SCO --> &hdev->lock --> hci_cb_list_lock

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(hci_cb_list_lock);
                               lock(&hdev->lock);
                               lock(hci_cb_list_lock);
  lock(sk_lock-AF_BLUETOOTH-BTPROTO_SCO);

 *** DEADLOCK ***

4 locks held by syz-executor373/5099:
 #0: ffffffff8e5041a8 (rfkill_global_mutex){+.+.}-{3:3}, at: rfkill_fop_write+0x160/0x570 net/rfkill/core.c:1278
 #1: ffff888022d6d028 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close+0x29/0x70 net/bluetooth/hci_core.c:552
 #2: ffff888022d6c078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_close_sync+0x306/0x1200 net/bluetooth/hci_sync.c:4837
 #3: ffffffff8e2ff068 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1790 [inline]
 #3: ffffffff8e2ff068 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xd9/0x260 net/bluetooth/hci_conn.c:2437

stack backtrace:
CPU: 0 PID: 5099 Comm: syz-executor373 Not tainted 6.2.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/21/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd1/0x138 lib/dump_stack.c:106
 check_noncircular+0x25f/0x2e0 kernel/locking/lockdep.c:2177
 check_prev_add kernel/locking/lockdep.c:3097 [inline]
 check_prevs_add kernel/locking/lockdep.c:3216 [inline]
 validate_chain kernel/locking/lockdep.c:3831 [inline]
 __lock_acquire+0x2a43/0x56d0 kernel/locking/lockdep.c:5055
 lock_acquire kernel/locking/lockdep.c:5668 [inline]
 lock_acquire+0x1e3/0x630 kernel/locking/lockdep.c:5633
 lock_sock_nested+0x3a/0xf0 net/core/sock.c:3471
 lock_sock include/net/sock.h:1725 [inline]
 sco_conn_del+0x12c/0x2b0 net/bluetooth/sco.c:197
 sco_disconn_cfm+0x75/0xb0 net/bluetooth/sco.c:1379
 hci_disconn_cfm include/net/bluetooth/hci_core.h:1793 [inline]
 hci_conn_hash_flush+0x126/0x260 net/bluetooth/hci_conn.c:2437
 hci_dev_close_sync+0x5fb/0x1200 net/bluetooth/hci_sync.c:4850
 hci_dev_do_close+0x31/0x70 net/bluetooth/hci_core.c:554
 hci_rfkill_set_block+0x161/0x1d0 net/bluetooth/hci_core.c:956
 rfkill_set_block+0x1f9/0x540 net/rfkill/core.c:345
 rfkill_fop_write+0x2c7/0x570 net/rfkill/core.c:1286
 vfs_write+0x2db/0xdd0 fs/read_write.c:582
 ksys_write+0x1ec/0x250 fs/read_write.c:637
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fc80e6ab529
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 d1 15 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffc20514578 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fc80e6ab529
RDX: 0000000000000008 RSI: 0000000020000080 RDI: 0000000000000003
RBP: 0000000000000003 R08: 0000000000000150 R09: 0000000000000150
R10: 0000000000000150 R11: 0000000000000246 R12: 00005555569b22b8
R13: 0000000000000011 R14: 00007ffc205145e0 R15: 0000000000000003
 </TASK>

Crashes (279):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/02/20 13:03 upstream c9c3395d5e3d bcdf85f8 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in sco_conn_del
2022/12/29 03:22 upstream 1b929c02afd3 44712fbc .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in sco_conn_del
2022/11/15 02:35 upstream 094226ad94f4 943f4cb8 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in sco_conn_del
2022/09/05 19:38 upstream 7e18e42e4b28 922294ab .config strace log report syz C ci-upstream-kasan-gce-root possible deadlock in sco_conn_del
2022/08/15 06:29 upstream 7ebfc85e2cd7 8dfcaa3d .config strace log report syz C ci-upstream-kasan-gce-smack-root possible deadlock in sco_conn_del
2022/08/07 09:26 upstream 200e340f2196 88e3a122 .config strace log report syz C ci-upstream-kasan-gce-smack-root possible deadlock in sco_conn_del
2022/08/05 12:37 upstream 200e340f2196 1c9013ac .config console log report syz C ci-upstream-kasan-gce-smack-root possible deadlock in sco_conn_del
2022/06/29 08:35 upstream 941e3e791269 496a8536 .config strace log report syz C ci-upstream-kasan-gce-root possible deadlock in sco_conn_del
2022/06/20 11:22 upstream a111daf0c53a 8f633d84 .config strace log report syz C ci-upstream-kasan-gce-root possible deadlock in sco_conn_del
2022/11/19 16:45 linux-next 15f3bff12cf6 5bb70014 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in sco_conn_del
2022/08/04 01:17 linux-next cb71b93c2dc3 1c9013ac .config strace log report syz C ci-upstream-linux-next-kasan-gce-root possible deadlock in sco_conn_del
2022/04/11 18:50 linux-next d12d7e1cfe38 af01ee7d .config console log report syz C ci-upstream-linux-next-kasan-gce-root possible deadlock in sco_conn_del
2022/10/10 05:52 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci bbed346d5a96 aea5da89 .config console log report syz C [disk image] [vmlinux] ci-upstream-gce-arm64 possible deadlock in sco_conn_del
2022/09/06 07:10 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 85413d1e802e 9dcd38fc .config console log report syz C ci-upstream-gce-arm64 possible deadlock in sco_conn_del
2022/09/04 02:22 upstream d895ec7938c4 28811d0a .config strace log report syz [disk image] [vmlinux] ci-upstream-kasan-gce-selinux-root possible deadlock in sco_conn_del
2023/01/01 09:52 upstream e4cf7c25bae5 ab32d508 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in sco_conn_del
2023/04/13 18:14 upstream de4664485abb 3cfcaa1b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in sco_conn_del
2023/04/10 07:13 upstream 09a9639e56c0 71147e29 .config console log report info ci-qemu-upstream possible deadlock in sco_conn_del
2023/04/05 19:36 upstream 99ddf2254feb 8b834965 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in sco_conn_del
2023/03/27 22:34 upstream 91fe204578ba 47f3aaf1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in sco_conn_del
2023/03/27 12:35 upstream 197b6b60ae7b f8f96aa9 .config console log report info ci-upstream-kasan-gce-smack-root possible deadlock in sco_conn_del
2023/03/21 11:41 upstream 17214b70a159 03fb9538 .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in sco_conn_del
2023/03/04 05:42 upstream 0a3f9a6b0265 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in sco_conn_del
2023/03/01 23:45 upstream 1d2aea1bcf68 f8902b57 .config console log report info ci-qemu-upstream possible deadlock in sco_conn_del
2023/02/28 12:20 upstream ae3419fbac84 95aee97a .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in sco_conn_del
2023/02/28 07:34 upstream ae3419fbac84 95aee97a .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in sco_conn_del
2023/02/25 07:04 upstream a93e884edf61 ee50e71c .config console log report info ci-upstream-kasan-gce-root possible deadlock in sco_conn_del
2023/02/21 17:54 upstream 89f5349e0673 f949448d .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in sco_conn_del
2023/02/16 17:42 upstream 033c40a89f55 7338e3c4 .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in sco_conn_del
2023/02/13 12:53 upstream ceaa837f96ad 4d66ad72 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in sco_conn_del
2023/02/11 13:08 upstream 420b2d431d18 93e26d60 .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in sco_conn_del
2023/02/09 04:49 upstream 0983f6bf2bfc 14a312c8 .config console log report info ci-qemu-upstream possible deadlock in sco_conn_del
2023/02/06 20:48 upstream d2d11f342b17 0a9c11b6 .config console log report info ci-qemu-upstream possible deadlock in sco_conn_del
2023/02/04 13:32 upstream 0136d86b7852 be607b78 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in sco_conn_del
2023/01/30 04:35 upstream ab072681eabe 9dfcf09c .config console log report info ci-upstream-kasan-gce-smack-root possible deadlock in sco_conn_del
2023/01/28 03:45 upstream 83abd4d4c4be 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in sco_conn_del
2023/01/26 21:19 upstream 7c46948a6e9c 9dfcf09c .config console log report info ci-upstream-kasan-gce-selinux-root possible deadlock in sco_conn_del
2023/01/26 14:48 upstream 7c46948a6e9c 7374c4e5 .config console log report info ci-qemu-upstream possible deadlock in sco_conn_del
2023/01/24 03:09 upstream 7bf70dbb1882 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in sco_conn_del
2023/01/22 04:31 upstream f67144022885 559a440a .config console log report info ci-upstream-kasan-gce-root possible deadlock in sco_conn_del
2023/01/21 01:49 upstream edc00350d205 7374c4e5 .config console log report info ci-qemu-upstream possible deadlock in sco_conn_del
2023/01/18 15:25 upstream c1649ec55708 42660d9e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in sco_conn_del
2023/01/17 04:40 upstream d532dd102151 a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in sco_conn_del
2023/01/11 18:43 upstream 7dd4b804e080 96166539 .config console log report info ci-upstream-kasan-gce-smack-root possible deadlock in sco_conn_del
2023/03/28 17:24 upstream 3a93e40326c8 48c74771 .config console log report info ci-qemu-upstream-386 possible deadlock in sco_conn_del
2023/03/04 08:02 upstream 0988a0ea7919 f8902b57 .config console log report info ci-qemu-upstream-386 possible deadlock in sco_conn_del
2023/01/28 18:11 upstream 5af6ce704936 7374c4e5 .config console log report info ci-qemu-upstream-386 possible deadlock in sco_conn_del
2023/01/13 17:38 upstream d863f0539b52 529798b0 .config console log report info ci-qemu-upstream-386 possible deadlock in sco_conn_del
2023/03/30 06:22 net 8c495270845d f325deb0 .config console log report info ci-upstream-net-this-kasan-gce possible deadlock in sco_conn_del
2023/03/21 18:43 net f038f3917baf 03fb9538 .config console log report info ci-upstream-net-this-kasan-gce possible deadlock in sco_conn_del
2023/03/08 17:02 net cdd28833100c d2b00170 .config console log report info ci-upstream-net-this-kasan-gce possible deadlock in sco_conn_del
2023/02/08 06:37 net-old 565b4824c39f 15c3d445 .config console log report info ci-upstream-net-this-kasan-gce possible deadlock in sco_conn_del
2023/02/05 18:30 net-old a05e7a67986c be607b78 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in sco_conn_del
2023/01/23 12:18 net-old e38553bdc377 44388686 .config console log report info ci-upstream-net-this-kasan-gce possible deadlock in sco_conn_del
2023/01/20 22:51 net-old 45a919bbb21c 559a440a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in sco_conn_del
2023/01/17 05:51 net-old 87b93b678e95 a63719e7 .config console log report info ci-upstream-net-this-kasan-gce possible deadlock in sco_conn_del
2023/01/12 18:54 net-old ae9dcb91c606 96166539 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in sco_conn_del
2023/04/06 09:05 net-next b536f32b5b03 08707520 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sco_conn_del
2023/04/03 02:23 net-next 51aaa68222d6 f325deb0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sco_conn_del
2023/03/24 15:41 net-next 323fe43cf9ae 9700afae .config console log report info ci-upstream-net-kasan-gce possible deadlock in sco_conn_del
2023/03/22 20:34 net-next 56c874f7dbca d846e076 .config console log report info ci-upstream-net-kasan-gce possible deadlock in sco_conn_del
2023/02/22 14:49 net-next-old 5b7c4cabbb65 409945bc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in sco_conn_del
2023/02/08 03:02 net-next-old ca8e4cbff6d5 15c3d445 .config console log report info ci-upstream-net-kasan-gce possible deadlock in sco_conn_del
2023/02/04 11:37 net-next-old dfefcb0c0417 1b2f701a .config console log report info ci-upstream-net-kasan-gce possible deadlock in sco_conn_del
2023/01/27 09:02 net-next-old 0313afe8b83a 9dfcf09c .config console log report info ci-upstream-net-kasan-gce possible deadlock in sco_conn_del
2023/01/24 00:16 net-next-old 40e0b0908142 9dfcf09c .config console log report info ci-upstream-net-kasan-gce possible deadlock in sco_conn_del
2023/01/16 20:43 net-next-old 5129bd8e8840 a63719e7 .config console log report info ci-upstream-net-kasan-gce possible deadlock in sco_conn_del
2023/01/23 20:27 linux-next 691781f561e9 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in sco_conn_del
2022/04/04 03:35 linux-next 696206280c5e 79a2a8fc .config console log report info ci-upstream-linux-next-kasan-gce-root possible deadlock in sco_conn_del
2022/04/03 22:02 linux-next e5071887cd22 79a2a8fc .config console log report info ci-upstream-linux-next-kasan-gce-root possible deadlock in sco_conn_del
2023/03/29 16:20 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 59caa87f9dfb f325deb0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in sco_conn_del
2023/03/27 21:30 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci e8d018dd0257 47f3aaf1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in sco_conn_del
2023/02/10 20:45 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2d3827b3f393 95871dcc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in sco_conn_del
2023/02/08 10:21 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci eaed33698e35 15c3d445 .config console log report info ci-upstream-gce-arm64 possible deadlock in sco_conn_del
2023/01/24 16:37 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2e84eedb182e 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in sco_conn_del
2023/01/14 13:52 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 9598c377d828 a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in sco_conn_del
* Struck through repros no longer work on HEAD.