syzbot


possible deadlock in rfcomm_dlc_exists

Status: upstream: reported C repro on 2023/01/20 16:28
Subsystems: bluetooth
[Documentation on labels]
Reported-by: syzbot+b69a625d06e8ece26415@syzkaller.appspotmail.com
First crash: 463d, last: 1h23m
Cause bisection: failed (error log, bisect log)
  
Discussions (14)
Title Replies (including bot) Last reply
[syzbot] Monthly bluetooth report (Apr 2024) 0 (1) 2024/04/08 12:51
[syzbot] Monthly bluetooth report (Mar 2024) 0 (1) 2024/03/06 22:08
[syzbot] Monthly bluetooth report (Feb 2024) 0 (1) 2024/02/04 13:30
[syzbot] Monthly bluetooth report (Jan 2024) 0 (1) 2024/01/04 11:26
[syzbot] Monthly bluetooth report (Dec 2023) 0 (1) 2023/12/04 12:38
[syzbot] Monthly bluetooth report (Nov 2023) 0 (1) 2023/11/03 10:22
[syzbot] Monthly bluetooth report (Oct 2023) 0 (1) 2023/10/02 12:39
[syzbot] Monthly bluetooth report (Sep 2023) 0 (1) 2023/09/01 08:50
[syzbot] Monthly bluetooth report (Aug 2023) 0 (1) 2023/08/01 12:53
[syzbot] Monthly bluetooth report (Jun 2023) 0 (1) 2023/07/01 10:15
[syzbot] Monthly bluetooth report (May 2023) 0 (1) 2023/05/30 20:52
[syzbot] Monthly bluetooth report (Apr 2023) 0 (1) 2023/04/30 08:00
[syzbot] possible deadlock in rfcomm_dlc_exists 0 (2) 2023/03/31 00:21
[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-5.15 possible deadlock in rfcomm_dlc_exists C 305 5h38m 397d 0/3 upstream: reported C repro on 2023/03/23 21:28
linux-6.1 possible deadlock in rfcomm_dlc_exists 258 1d23h 397d 0/3 upstream: reported on 2023/03/24 03:20
Last patch testing requests (3)
Created Duration User Patch Repo Result
2023/03/31 08:49 22m hdanton@sina.com patch https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git a6d9e3034536 OK log
2023/03/31 08:01 13m hdanton@sina.com patch https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git a6d9e3034536 report log
2023/03/31 03:20 13m hdanton@sina.com patch https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git a6d9e3034536 report log

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
6.8.0-syzkaller-08951-gfe46a7dd189e #0 Not tainted
------------------------------------------------------
syz-executor237/5105 is trying to acquire lock:
ffffffff8f58c328 (rfcomm_mutex){+.+.}-{3:3}, at: rfcomm_dlc_exists+0x5f/0x1a0 net/bluetooth/rfcomm/core.c:546

but task is already holding lock:
ffffffff8f5912a8 (rfcomm_ioctl_mutex){+.+.}-{3:3}, at: rfcomm_create_dev net/bluetooth/rfcomm/tty.c:484 [inline]
ffffffff8f5912a8 (rfcomm_ioctl_mutex){+.+.}-{3:3}, at: rfcomm_dev_ioctl+0x8e4/0x1c80 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:608 [inline]
       __mutex_lock+0x175/0x9c0 kernel/locking/mutex.c:752
       rfcomm_create_dev net/bluetooth/rfcomm/tty.c:484 [inline]
       rfcomm_dev_ioctl+0x8e4/0x1c80 net/bluetooth/rfcomm/tty.c:587
       rfcomm_sock_ioctl+0xb4/0xe0 net/bluetooth/rfcomm/sock.c:873
       sock_do_ioctl+0x119/0x280 net/socket.c:1222
       sock_ioctl+0x22e/0x6c0 net/socket.c:1341
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:904 [inline]
       __se_sys_ioctl fs/ioctl.c:890 [inline]
       __x64_sys_ioctl+0x196/0x220 fs/ioctl.c:890
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0xd5/0x260 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x6d/0x75

-> #2 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}:
       lock_sock_nested+0x3a/0xf0 net/core/sock.c:3535
       lock_sock include/net/sock.h:1671 [inline]
       rfcomm_sk_state_change+0x6d/0x3b0 net/bluetooth/rfcomm/sock.c:73
       __rfcomm_dlc_close+0x28f/0x720 net/bluetooth/rfcomm/core.c:493
       rfcomm_dlc_close+0x1eb/0x240 net/bluetooth/rfcomm/core.c:524
       __rfcomm_sock_close+0xa7/0x230 net/bluetooth/rfcomm/sock.c:220
       rfcomm_sock_shutdown+0xd5/0x230 net/bluetooth/rfcomm/sock.c:905
       rfcomm_sock_release+0x5d/0x140 net/bluetooth/rfcomm/sock.c:926
       __sock_release+0xb3/0x270 net/socket.c:659
       sock_close+0x1c/0x30 net/socket.c:1421
       __fput+0x273/0xb80 fs/file_table.c:422
       task_work_run+0x151/0x250 kernel/task_work.c:180
       exit_task_work include/linux/task_work.h:38 [inline]
       do_exit+0xa7d/0x2be0 kernel/exit.c:878
       do_group_exit+0xd3/0x2a0 kernel/exit.c:1027
       get_signal+0x2390/0x2760 kernel/signal.c:2907
       arch_do_signal_or_restart+0x90/0x7e0 arch/x86/kernel/signal.c:310
       exit_to_user_mode_loop kernel/entry/common.c:105 [inline]
       exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
       __syscall_exit_to_user_mode_work kernel/entry/common.c:201 [inline]
       syscall_exit_to_user_mode+0x14a/0x2a0 kernel/entry/common.c:212
       do_syscall_64+0xe2/0x260 arch/x86/entry/common.c:89
       entry_SYSCALL_64_after_hwframe+0x6d/0x75

-> #1 (&d->lock){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:608 [inline]
       __mutex_lock+0x175/0x9c0 kernel/locking/mutex.c:752
       __rfcomm_dlc_close+0x235/0x720 net/bluetooth/rfcomm/core.c:491
       rfcomm_dlc_close+0x1eb/0x240 net/bluetooth/rfcomm/core.c:524
       __rfcomm_sock_close+0xa7/0x230 net/bluetooth/rfcomm/sock.c:220
       rfcomm_sock_shutdown+0xd5/0x230 net/bluetooth/rfcomm/sock.c:905
       rfcomm_sock_release+0x5d/0x140 net/bluetooth/rfcomm/sock.c:926
       __sock_release+0xb3/0x270 net/socket.c:659
       sock_close+0x1c/0x30 net/socket.c:1421
       __fput+0x273/0xb80 fs/file_table.c:422
       task_work_run+0x151/0x250 kernel/task_work.c:180
       exit_task_work include/linux/task_work.h:38 [inline]
       do_exit+0xa7d/0x2be0 kernel/exit.c:878
       do_group_exit+0xd3/0x2a0 kernel/exit.c:1027
       get_signal+0x2390/0x2760 kernel/signal.c:2907
       arch_do_signal_or_restart+0x90/0x7e0 arch/x86/kernel/signal.c:310
       exit_to_user_mode_loop kernel/entry/common.c:105 [inline]
       exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
       __syscall_exit_to_user_mode_work kernel/entry/common.c:201 [inline]
       syscall_exit_to_user_mode+0x14a/0x2a0 kernel/entry/common.c:212
       do_syscall_64+0xe2/0x260 arch/x86/entry/common.c:89
       entry_SYSCALL_64_after_hwframe+0x6d/0x75

-> #0 (rfcomm_mutex){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3134 [inline]
       check_prevs_add kernel/locking/lockdep.c:3253 [inline]
       validate_chain kernel/locking/lockdep.c:3869 [inline]
       __lock_acquire+0x2478/0x3b30 kernel/locking/lockdep.c:5137
       lock_acquire kernel/locking/lockdep.c:5754 [inline]
       lock_acquire+0x1b1/0x540 kernel/locking/lockdep.c:5719
       __mutex_lock_common kernel/locking/mutex.c:608 [inline]
       __mutex_lock+0x175/0x9c0 kernel/locking/mutex.c:752
       rfcomm_dlc_exists+0x5f/0x1a0 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+0x9c5/0x1c80 net/bluetooth/rfcomm/tty.c:587
       rfcomm_sock_ioctl+0xb4/0xe0 net/bluetooth/rfcomm/sock.c:873
       sock_do_ioctl+0x119/0x280 net/socket.c:1222
       sock_ioctl+0x22e/0x6c0 net/socket.c:1341
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:904 [inline]
       __se_sys_ioctl fs/ioctl.c:890 [inline]
       __x64_sys_ioctl+0x196/0x220 fs/ioctl.c:890
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0xd5/0x260 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x6d/0x75

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-executor237/5105:
 #0: ffff88802ade4258 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1671 [inline]
 #0: ffff88802ade4258 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: rfcomm_sock_ioctl+0xa7/0xe0 net/bluetooth/rfcomm/sock.c:872
 #1: ffffffff8f5912a8 (rfcomm_ioctl_mutex){+.+.}-{3:3}, at: rfcomm_create_dev net/bluetooth/rfcomm/tty.c:484 [inline]
 #1: ffffffff8f5912a8 (rfcomm_ioctl_mutex){+.+.}-{3:3}, at: rfcomm_dev_ioctl+0x8e4/0x1c80 net/bluetooth/rfcomm/tty.c:587

stack backtrace:
CPU: 1 PID: 5105 Comm: syz-executor237 Not tainted 6.8.0-syzkaller-08951-gfe46a7dd189e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:114
 check_noncircular+0x31a/0x400 kernel/locking/lockdep.c:2187
 check_prev_add kernel/locking/lockdep.c:3134 [inline]
 check_prevs_add kernel/locking/lockdep.c:3253 [inline]
 validate_chain kernel/locking/lockdep.c:3869 [inline]
 __lock_acquire+0x2478/0x3b30 kernel/locking/lockdep.c:5137
 lock_acquire kernel/locking/lockdep.c:5754 [inline]
 lock_acquire+0x1b1/0x540 kernel/locking/lockdep.c:5719
 __mutex_lock_common kernel/locking/mutex.c:608 [inline]
 __mutex_lock+0x175/0x9c0 kernel/locking/mutex.c:752
 rfcomm_dlc_exists+0x5f/0x1a0 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+0x9c5/0x1c80 net/bluetooth/rfcomm/tty.c:587
 rfcomm_sock_ioctl+0xb4/0xe0 net/bluetooth/rfcomm/sock.c:873
 sock_do_ioctl+0x119/0x280 net/socket.c:1222
 sock_ioctl+0x22e/0x6c0 net/socket.c:1341
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:904 [inline]
 __se_sys_ioctl fs/ioctl.c:890 [inline]
 __x64_sys_ioctl+0x196/0x220 fs/ioctl.c:890
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xd5/0x260 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x6d/0x75
RIP: 0033:0x7f6140612d49
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 11 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe334cb378 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f6140612d49
RDX: 0000000020000100 RSI: 00000000400452c8 RDI: 0000000000000005
RBP: 00000000000f4240 R08: 0000000000000000 R09: 0000555500000000
R10: 0000555500000000 R11: 0000000000000246 R12: 00007ffe334cb3c0
R13: 00007ffe334cb3d0 R14: 000000000002da18 R15: 00007ffe334cb390
 </TASK>

Crashes (12013):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/03/24 23:08 upstream fe46a7dd189e 0ea90952 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in rfcomm_dlc_exists
2024/03/24 21:03 upstream fe46a7dd189e 0ea90952 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in rfcomm_dlc_exists
2024/03/16 10:50 upstream fe46a7dd189e d615901c .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in rfcomm_dlc_exists
2024/03/06 22:40 upstream 5847c9777c30 f39a7eed .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_dlc_exists
2023/10/17 14:10 upstream 213f891525c2 342b9c55 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_dlc_exists
2023/11/24 06:22 net c9213ddad2bd 5b429f39 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_dlc_exists
2023/11/14 21:35 net 48c205c69ac9 cb976f63 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_dlc_exists
2023/11/04 14:08 net 016b9332a334 500bfdc4 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_dlc_exists
2023/11/01 05:47 net 55c900477f5b 69904c9f .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_dlc_exists
2023/12/20 02:05 net-next f7dd48ea76be 3ad490ea .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_dlc_exists
2023/11/14 23:32 net-next 89cdf9d55601 cb976f63 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_dlc_exists
2023/11/14 21:36 net-next 89cdf9d55601 cb976f63 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_dlc_exists
2023/11/04 06:23 net-next ff269e2cd5ad 500bfdc4 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_dlc_exists
2023/10/17 09:55 net-next 90de47f020db 342b9c55 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_dlc_exists
2023/03/31 00:20 linux-next a6d9e3034536 f325deb0 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in rfcomm_dlc_exists
2024/04/24 12:50 upstream 9d1ddab261f3 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in rfcomm_dlc_exists
2024/04/24 11:14 upstream 9d1ddab261f3 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_dlc_exists
2024/04/24 08:03 upstream 9d1ddab261f3 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in rfcomm_dlc_exists
2024/04/24 05:10 upstream 9d1ddab261f3 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in rfcomm_dlc_exists
2024/04/24 03:36 upstream 9d1ddab261f3 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_dlc_exists
2024/04/24 02:16 upstream 9d1ddab261f3 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_dlc_exists
2024/04/24 02:16 upstream 9d1ddab261f3 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_dlc_exists
2024/04/23 23:12 upstream 71b1543c83d6 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in rfcomm_dlc_exists
2024/04/23 21:53 upstream 71b1543c83d6 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_dlc_exists
2024/04/23 20:27 upstream 71b1543c83d6 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_dlc_exists
2024/04/23 16:27 upstream 71b1543c83d6 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_dlc_exists
2024/04/23 16:15 upstream 71b1543c83d6 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in rfcomm_dlc_exists
2024/04/23 12:20 upstream 4d2008430ce8 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in rfcomm_dlc_exists
2024/04/23 05:42 upstream 4d2008430ce8 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in rfcomm_dlc_exists
2024/04/23 04:01 upstream 4d2008430ce8 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_dlc_exists
2024/04/23 02:06 upstream 4d2008430ce8 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in rfcomm_dlc_exists
2024/04/23 01:03 upstream 4d2008430ce8 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_dlc_exists
2024/04/23 00:03 upstream 4d2008430ce8 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_dlc_exists
2024/04/22 23:41 upstream 4d2008430ce8 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_dlc_exists
2024/04/22 09:43 upstream 48cf398f15fc af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_dlc_exists
2024/04/22 06:21 upstream 48cf398f15fc af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_dlc_exists
2024/04/22 03:16 upstream 48cf398f15fc af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_dlc_exists
2024/04/21 21:10 upstream 3b68086599f8 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in rfcomm_dlc_exists
2024/04/21 21:03 upstream 48cf398f15fc af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_dlc_exists
2024/04/21 19:59 upstream 3b68086599f8 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in rfcomm_dlc_exists
2024/04/22 01:29 upstream 48cf398f15fc af24b050 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in rfcomm_dlc_exists
2024/04/23 09:29 upstream a2c63a3f3d68 21339d7b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in rfcomm_dlc_exists
2024/04/22 22:25 upstream a2c63a3f3d68 21339d7b .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in rfcomm_dlc_exists
2024/04/21 18:04 upstream 3b68086599f8 af24b050 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in rfcomm_dlc_exists
2024/04/21 11:22 upstream 977b1ef51866 af24b050 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in rfcomm_dlc_exists
2024/04/22 17:17 net f99c5f563c17 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_dlc_exists
2024/04/22 15:28 net f99c5f563c17 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_dlc_exists
2024/04/22 13:59 net f99c5f563c17 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_dlc_exists
2024/04/22 12:25 net f99c5f563c17 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_dlc_exists
2024/04/22 10:59 net f99c5f563c17 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_dlc_exists
2024/04/22 08:52 net f99c5f563c17 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_dlc_exists
2024/04/22 04:17 net f99c5f563c17 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_dlc_exists
2024/04/22 02:49 net f99c5f563c17 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_dlc_exists
2024/04/21 23:47 net f99c5f563c17 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_dlc_exists
2024/04/21 16:58 net f99c5f563c17 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_dlc_exists
2024/04/21 15:38 net f99c5f563c17 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_dlc_exists
2024/04/21 15:08 net f99c5f563c17 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_dlc_exists
2024/04/21 14:07 net f99c5f563c17 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_dlc_exists
2024/04/21 13:01 net f99c5f563c17 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_dlc_exists
2024/04/21 11:54 net f99c5f563c17 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_dlc_exists
2024/03/29 07:27 net-next 237bb5f7f7f5 120789fd .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_dlc_exists
2024/04/24 06:29 linux-next 7b4f2bc91c15 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in rfcomm_dlc_exists
2024/04/24 00:58 linux-next 7b4f2bc91c15 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in rfcomm_dlc_exists
2024/04/23 06:59 linux-next 7b4f2bc91c15 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in rfcomm_dlc_exists
2024/04/22 07:33 linux-next 7b4f2bc91c15 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in rfcomm_dlc_exists
2024/04/21 18:59 linux-next 7b4f2bc91c15 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in rfcomm_dlc_exists
2024/04/22 16:11 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 6a71d2909427 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_dlc_exists
2024/04/21 22:12 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 6a71d2909427 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_dlc_exists
2023/01/16 16:23 linux-next c12e2e5b76b2 a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in rfcomm_dlc_exists
* Struck through repros no longer work on HEAD.