syzbot


possible deadlock in rfcomm_dlc_exists

Status: upstream: reported on 2023/01/20 16:28
Subsystems: bluetooth (incorrect?)
Reported-by: syzbot+b69a625d06e8ece26415@syzkaller.appspotmail.com
First crash: 65d, last: 4h58m

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
6.3.0-rc2-syzkaller-00047-g6015b1aca1a2 #0 Not tainted
------------------------------------------------------
syz-executor.5/9079 is trying to acquire lock:
ffffffff8e350348 (rfcomm_mutex){+.+.}-{3:3}, at: rfcomm_dlc_exists+0x58/0x190 net/bluetooth/rfcomm/core.c:546

but task is already holding lock:
ffffffff8e355308 (rfcomm_ioctl_mutex){+.+.}-{3:3}, at: rfcomm_create_dev net/bluetooth/rfcomm/tty.c:484 [inline]
ffffffff8e355308 (rfcomm_ioctl_mutex){+.+.}-{3:3}, at: rfcomm_dev_ioctl+0x8a2/0x1c00 net/bluetooth/rfcomm/tty.c:587

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (rfcomm_ioctl_mutex){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x12f/0x1350 kernel/locking/mutex.c:747
       rfcomm_create_dev net/bluetooth/rfcomm/tty.c:484 [inline]
       rfcomm_dev_ioctl+0x8a2/0x1c00 net/bluetooth/rfcomm/tty.c:587
       rfcomm_sock_ioctl+0xb7/0xe0 net/bluetooth/rfcomm/sock.c:880
       sock_do_ioctl+0xcc/0x230 net/socket.c:1199
       sock_ioctl+0x1f8/0x680 net/socket.c:1316
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:870 [inline]
       __se_sys_ioctl fs/ioctl.c:856 [inline]
       __x64_sys_ioctl+0x197/0x210 fs/ioctl.c:856
       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

-> #2 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}:
       lock_sock_nested+0x3a/0xf0 net/core/sock.c:3474
       lock_sock include/net/sock.h:1697 [inline]
       rfcomm_sk_state_change+0x6d/0x3a0 net/bluetooth/rfcomm/sock.c:73
       __rfcomm_dlc_close+0x1b1/0x890 net/bluetooth/rfcomm/core.c:493
       rfcomm_dlc_close+0x1e9/0x240 net/bluetooth/rfcomm/core.c:524
       __rfcomm_sock_close+0x17a/0x2f0 net/bluetooth/rfcomm/sock.c:220
       rfcomm_sock_shutdown+0xd8/0x230 net/bluetooth/rfcomm/sock.c:912
       rfcomm_sock_release+0x68/0x140 net/bluetooth/rfcomm/sock.c:933
       __sock_release+0xcd/0x290 net/socket.c:653
       sock_close+0x1c/0x20 net/socket.c:1395
       __fput+0x27c/0xa90 fs/file_table.c:321
       task_work_run+0x16f/0x270 kernel/task_work.c:179
       get_signal+0x1c7/0x25b0 kernel/signal.c:2635
       arch_do_signal_or_restart+0x79/0x5c0 arch/x86/kernel/signal.c:306
       exit_to_user_mode_loop kernel/entry/common.c:168 [inline]
       exit_to_user_mode_prepare+0x15f/0x250 kernel/entry/common.c:203
       __syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline]
       syscall_exit_to_user_mode+0x1d/0x50 kernel/entry/common.c:296
       do_syscall_64+0x46/0xb0 arch/x86/entry/common.c:86
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #1 (&d->lock){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x12f/0x1350 kernel/locking/mutex.c:747
       __rfcomm_dlc_close+0x15d/0x890 net/bluetooth/rfcomm/core.c:491
       rfcomm_dlc_close+0x1e9/0x240 net/bluetooth/rfcomm/core.c:524
       __rfcomm_sock_close+0x17a/0x2f0 net/bluetooth/rfcomm/sock.c:220
       rfcomm_sock_shutdown+0xd8/0x230 net/bluetooth/rfcomm/sock.c:912
       rfcomm_sock_release+0x68/0x140 net/bluetooth/rfcomm/sock.c:933
       __sock_release+0xcd/0x290 net/socket.c:653
       sock_close+0x1c/0x20 net/socket.c:1395
       __fput+0x27c/0xa90 fs/file_table.c:321
       task_work_run+0x16f/0x270 kernel/task_work.c:179
       get_signal+0x1c7/0x25b0 kernel/signal.c:2635
       arch_do_signal_or_restart+0x79/0x5c0 arch/x86/kernel/signal.c:306
       exit_to_user_mode_loop kernel/entry/common.c:168 [inline]
       exit_to_user_mode_prepare+0x15f/0x250 kernel/entry/common.c:203
       __syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline]
       syscall_exit_to_user_mode+0x1d/0x50 kernel/entry/common.c:296
       do_syscall_64+0x46/0xb0 arch/x86/entry/common.c:86
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #0 (rfcomm_mutex){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3098 [inline]
       check_prevs_add kernel/locking/lockdep.c:3217 [inline]
       validate_chain kernel/locking/lockdep.c:3832 [inline]
       __lock_acquire+0x2ec7/0x5d40 kernel/locking/lockdep.c:5056
       lock_acquire kernel/locking/lockdep.c:5669 [inline]
       lock_acquire+0x1af/0x520 kernel/locking/lockdep.c:5634
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x12f/0x1350 kernel/locking/mutex.c:747
       rfcomm_dlc_exists+0x58/0x190 net/bluetooth/rfcomm/core.c:546
       __rfcomm_create_dev net/bluetooth/rfcomm/tty.c:414 [inline]
       rfcomm_create_dev net/bluetooth/rfcomm/tty.c:485 [inline]
       rfcomm_dev_ioctl+0x966/0x1c00 net/bluetooth/rfcomm/tty.c:587
       rfcomm_sock_ioctl+0xb7/0xe0 net/bluetooth/rfcomm/sock.c:880
       sock_do_ioctl+0xcc/0x230 net/socket.c:1199
       sock_ioctl+0x1f8/0x680 net/socket.c:1316
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:870 [inline]
       __se_sys_ioctl fs/ioctl.c:856 [inline]
       __x64_sys_ioctl+0x197/0x210 fs/ioctl.c:856
       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:
  rfcomm_mutex --> sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM --> rfcomm_ioctl_mutex

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(rfcomm_ioctl_mutex);
                               lock(sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM);
                               lock(rfcomm_ioctl_mutex);
  lock(rfcomm_mutex);

 *** DEADLOCK ***

2 locks held by syz-executor.5/9079:
 #0: ffff88807d76f130 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1697 [inline]
 #0: ffff88807d76f130 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: rfcomm_sock_ioctl+0xaa/0xe0 net/bluetooth/rfcomm/sock.c:879
 #1: ffffffff8e355308 (rfcomm_ioctl_mutex){+.+.}-{3:3}, at: rfcomm_create_dev net/bluetooth/rfcomm/tty.c:484 [inline]
 #1: ffffffff8e355308 (rfcomm_ioctl_mutex){+.+.}-{3:3}, at: rfcomm_dev_ioctl+0x8a2/0x1c00 net/bluetooth/rfcomm/tty.c:587

stack backtrace:
CPU: 1 PID: 9079 Comm: syz-executor.5 Not tainted 6.3.0-rc2-syzkaller-00047-g6015b1aca1a2 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106
 check_noncircular+0x25f/0x2e0 kernel/locking/lockdep.c:2178
 check_prev_add kernel/locking/lockdep.c:3098 [inline]
 check_prevs_add kernel/locking/lockdep.c:3217 [inline]
 validate_chain kernel/locking/lockdep.c:3832 [inline]
 __lock_acquire+0x2ec7/0x5d40 kernel/locking/lockdep.c:5056
 lock_acquire kernel/locking/lockdep.c:5669 [inline]
 lock_acquire+0x1af/0x520 kernel/locking/lockdep.c:5634
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x12f/0x1350 kernel/locking/mutex.c:747
 rfcomm_dlc_exists+0x58/0x190 net/bluetooth/rfcomm/core.c:546
 __rfcomm_create_dev net/bluetooth/rfcomm/tty.c:414 [inline]
 rfcomm_create_dev net/bluetooth/rfcomm/tty.c:485 [inline]
 rfcomm_dev_ioctl+0x966/0x1c00 net/bluetooth/rfcomm/tty.c:587
 rfcomm_sock_ioctl+0xb7/0xe0 net/bluetooth/rfcomm/sock.c:880
 sock_do_ioctl+0xcc/0x230 net/socket.c:1199
 sock_ioctl+0x1f8/0x680 net/socket.c:1316
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:870 [inline]
 __se_sys_ioctl fs/ioctl.c:856 [inline]
 __x64_sys_ioctl+0x197/0x210 fs/ioctl.c:856
 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:0x7f7258e8c0f9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 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:00007f7259b97168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f7258fac2c0 RCX: 00007f7258e8c0f9
RDX: 0000000020000100 RSI: 00000000400452c8 RDI: 0000000000000009
RBP: 00007f7258ee7b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fffa275317f R14: 00007f7259b97300 R15: 0000000000022000
 </TASK>

Crashes (69):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets Title
ci-upstream-kasan-gce-root 2023/03/15 11:24 upstream 6015b1aca1a2 0d5c4377 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/03/13 22:24 upstream fc89d7fb499b 026e2200 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/03/13 16:11 upstream eeac8ede1755 026e2200 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/03/13 07:20 upstream eeac8ede1755 5205ef30 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/03/02 22:08 upstream 04a357b1f6f0 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/03/02 01:25 upstream ee3f96b16468 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/02/28 21:39 upstream ae3419fbac84 95aee97a .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/02/28 19:53 upstream ae3419fbac84 95aee97a .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/02/28 05:01 upstream 982818426a0f 95aee97a .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/02/28 03:22 upstream 982818426a0f e792ae78 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/02/27 06:17 upstream f3a2439f20d9 ee50e71c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/02/26 18:17 upstream 2fcd07b7ccd5 ee50e71c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/02/26 04:37 upstream 1ec35eadc3b4 ee50e71c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/02/26 01:20 upstream 1ec35eadc3b4 ee50e71c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/02/25 02:23 upstream a93e884edf61 ee50e71c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/02/24 17:53 upstream d2980d8d8265 ee50e71c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-smack-root 2023/02/24 14:55 upstream d2980d8d8265 ee50e71c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-smack-root 2023/02/24 11:50 upstream d2980d8d8265 9e2ebb3c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-smack-root 2023/02/24 09:50 upstream d2980d8d8265 9e2ebb3c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/02/24 08:09 upstream d2980d8d8265 9e2ebb3c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/02/23 23:46 upstream a5c95ca18a98 9e2ebb3c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/02/23 19:16 upstream a5c95ca18a98 9e2ebb3c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-smack-root 2023/02/23 10:06 upstream d8ca6dbb8de7 9e2ebb3c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-smack-root 2023/02/20 19:37 upstream c9c3395d5e3d 4f5f5209 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-selinux-root 2023/02/16 22:36 upstream 3ac88fa4605e 851bc19a .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-smack-root 2023/02/15 07:55 upstream e1c04510f521 1d6b4af7 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-selinux-root 2023/02/15 07:30 upstream e1c04510f521 1d6b4af7 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/02/05 20:54 upstream 837c07cf68fe be607b78 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/02/05 06:13 upstream 95078069c1e7 be607b78 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/02/04 09:30 upstream 0136d86b7852 1b2f701a .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/02/02 07:12 upstream 9f266ccaa2f5 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/01/30 12:11 upstream 6d796c50f84c 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/01/29 08:45 upstream c96618275234 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-smack-root 2023/01/29 04:48 upstream c96618275234 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/01/29 04:32 upstream c96618275234 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-smack-root 2023/01/28 18:19 upstream 5af6ce704936 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/01/28 17:53 upstream 5af6ce704936 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-selinux-root 2023/01/28 08:03 upstream 83abd4d4c4be 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-smack-root 2023/01/28 04:07 upstream 83abd4d4c4be 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-kasan-gce-root 2023/01/22 21:40 upstream 2241ab53cbb5 559a440a .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-net-this-kasan-gce 2023/02/04 17:27 net a05e7a67986c be607b78 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-net-this-kasan-gce 2023/01/29 15:48 net a6efc42a86c0 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-net-kasan-gce 2023/02/07 02:20 net-next c21adf256f8d 0a9c11b6 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-net-kasan-gce 2023/02/06 19:00 net-next c21adf256f8d 0a9c11b6 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-net-kasan-gce 2023/02/06 11:55 net-next 8b7018fa7177 be607b78 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-net-kasan-gce 2023/01/29 23:27 net-next 70eb3911d80f 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-linux-next-kasan-gce-root 2023/02/27 13:19 linux-next 7f7a8831520f e792ae78 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-linux-next-kasan-gce-root 2023/02/23 11:19 linux-next 0222aa9800b2 9e2ebb3c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-linux-next-kasan-gce-root 2023/02/23 08:13 linux-next 0222aa9800b2 9e2ebb3c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-linux-next-kasan-gce-root 2023/02/23 01:58 linux-next aaf70d5ad5e2 409945bc .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-linux-next-kasan-gce-root 2023/02/23 01:58 linux-next aaf70d5ad5e2 409945bc .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-linux-next-kasan-gce-root 2023/02/22 20:53 linux-next aaf70d5ad5e2 409945bc .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-linux-next-kasan-gce-root 2023/02/20 16:43 linux-next d2af0fa4bfa4 4f5f5209 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-linux-next-kasan-gce-root 2023/02/20 14:06 linux-next d2af0fa4bfa4 bcdf85f8 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-linux-next-kasan-gce-root 2023/02/20 02:20 linux-next c068f40300a0 bcdf85f8 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-linux-next-kasan-gce-root 2023/02/16 03:09 linux-next 9d9019bcea1a 6be0f1f5 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-linux-next-kasan-gce-root 2023/01/16 16:23 linux-next c12e2e5b76b2 a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-gce-arm64 2023/03/22 11:26 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci fe15c26ee26e d846e076 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-gce-arm64 2023/02/24 01:24 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a9b06ec42c0f 9e2ebb3c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-gce-arm64 2023/02/21 09:44 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a9b06ec42c0f f949448d .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-gce-arm64 2023/02/20 14:51 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2d3827b3f393 4f5f5209 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-gce-arm64 2023/02/18 18:37 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2d3827b3f393 bcdf85f8 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-gce-arm64 2023/02/16 11:32 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2d3827b3f393 7338e3c4 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-gce-arm64 2023/02/08 15:19 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci eaed33698e35 fc9c934e .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-gce-arm64 2023/02/07 15:51 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci ca72d58361ee 15c3d445 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-gce-arm64 2023/02/04 17:07 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci ca72d58361ee be607b78 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
ci-upstream-gce-arm64 2023/01/30 21:43 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci c62c88e05937 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_dlc_exists
* Struck through repros no longer work on HEAD.