syzbot


possible deadlock in rfcomm_sk_state_change

Status: upstream: reported C repro on 2021/09/13 05:15
Reported-by: syzbot+d7ce59b06b3eb14fd218@syzkaller.appspotmail.com
First crash: 511d, last: 23h09m

Cause bisection: introduced by (bisect log) :
commit 1804fdf6e494e5e2938c65d8391690b59bcff897
Author: Tedd Ho-Jeong An <tedd.an@intel.com>
Date: Thu Aug 5 00:32:19 2021 +0000

  Bluetooth: btintel: Combine setting up MSFT extension

Crash: BUG: sleeping function called from invalid context in stack_depot_save (log)
Repro: C syz .config
Last patch testing requests:
Created Duration User Patch Repo Result
2021/10/10 13:34 11m phind.uet@gmail.com linux-next report log
2021/10/10 13:32 11m phind.uet@gmail.com linux-next report log

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
6.2.0-rc1-syzkaller-00084-gc8451c141e07 #0 Not tainted
------------------------------------------------------
syz-executor245/5091 is trying to acquire lock:
ffff88807db39130 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1725 [inline]
ffff88807db39130 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: rfcomm_sk_state_change+0x52/0x2f0 net/bluetooth/rfcomm/sock.c:73

but task is already holding lock:
ffff8880151a0928 (&d->lock){+.+.}-{3:3}, at: __rfcomm_dlc_close+0x276/0x470 net/bluetooth/rfcomm/core.c:487

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&d->lock){+.+.}-{3:3}:
       lock_acquire+0x1a7/0x400 kernel/locking/lockdep.c:5668
       __mutex_lock_common+0x1de/0x26c0 kernel/locking/mutex.c:603
       __mutex_lock kernel/locking/mutex.c:747 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799
       __rfcomm_dlc_close+0x276/0x470 net/bluetooth/rfcomm/core.c:487
       rfcomm_dlc_close+0x10d/0x1c0 net/bluetooth/rfcomm/core.c:520
       __rfcomm_sock_close+0x101/0x220 net/bluetooth/rfcomm/sock.c:220
       rfcomm_sock_shutdown+0xad/0x230 net/bluetooth/rfcomm/sock.c:907
       rfcomm_sock_release+0x55/0x120 net/bluetooth/rfcomm/sock.c:928
       __sock_release net/socket.c:650 [inline]
       sock_close+0xd7/0x260 net/socket.c:1365
       __fput+0x3ba/0x880 fs/file_table.c:320
       task_work_run+0x243/0x300 kernel/task_work.c:179
       exit_task_work include/linux/task_work.h:38 [inline]
       do_exit+0x644/0x2150 kernel/exit.c:867
       do_group_exit+0x1fd/0x2b0 kernel/exit.c:1012
       get_signal+0x1755/0x1820 kernel/signal.c:2859
       arch_do_signal_or_restart+0x8d/0x5f0 arch/x86/kernel/signal.c:306
       exit_to_user_mode_loop+0x74/0x160 kernel/entry/common.c:168
       exit_to_user_mode_prepare+0xad/0x110 kernel/entry/common.c:203
       __syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline]
       syscall_exit_to_user_mode+0x2e/0x60 kernel/entry/common.c:296
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #1 (rfcomm_mutex){+.+.}-{3:3}:
       lock_acquire+0x1a7/0x400 kernel/locking/lockdep.c:5668
       __mutex_lock_common+0x1de/0x26c0 kernel/locking/mutex.c:603
       __mutex_lock kernel/locking/mutex.c:747 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799
       rfcomm_dlc_open+0x25/0x50 net/bluetooth/rfcomm/core.c:425
       rfcomm_sock_connect+0x285/0x470 net/bluetooth/rfcomm/sock.c:413
       __sys_connect_file net/socket.c:1976 [inline]
       __sys_connect+0x29b/0x2d0 net/socket.c:1993
       __do_sys_connect net/socket.c:2003 [inline]
       __se_sys_connect net/socket.c:2000 [inline]
       __x64_sys_connect+0x76/0x80 net/socket.c:2000
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #0 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}:
       check_prev_add kernel/locking/lockdep.c:3097 [inline]
       check_prevs_add kernel/locking/lockdep.c:3216 [inline]
       validate_chain+0x184a/0x6470 kernel/locking/lockdep.c:3831
       __lock_acquire+0x1292/0x1f60 kernel/locking/lockdep.c:5055
       lock_acquire+0x1a7/0x400 kernel/locking/lockdep.c:5668
       lock_sock_nested+0x44/0xf0 net/core/sock.c:3470
       lock_sock include/net/sock.h:1725 [inline]
       rfcomm_sk_state_change+0x52/0x2f0 net/bluetooth/rfcomm/sock.c:73
       __rfcomm_dlc_close+0x2bb/0x470 net/bluetooth/rfcomm/core.c:489
       rfcomm_dlc_close+0x10d/0x1c0 net/bluetooth/rfcomm/core.c:520
       __rfcomm_sock_close+0x101/0x220 net/bluetooth/rfcomm/sock.c:220
       rfcomm_sock_shutdown+0xad/0x230 net/bluetooth/rfcomm/sock.c:907
       rfcomm_sock_release+0x55/0x120 net/bluetooth/rfcomm/sock.c:928
       __sock_release net/socket.c:650 [inline]
       sock_close+0xd7/0x260 net/socket.c:1365
       __fput+0x3ba/0x880 fs/file_table.c:320
       task_work_run+0x243/0x300 kernel/task_work.c:179
       exit_task_work include/linux/task_work.h:38 [inline]
       do_exit+0x644/0x2150 kernel/exit.c:867
       do_group_exit+0x1fd/0x2b0 kernel/exit.c:1012
       get_signal+0x1755/0x1820 kernel/signal.c:2859
       arch_do_signal_or_restart+0x8d/0x5f0 arch/x86/kernel/signal.c:306
       exit_to_user_mode_loop+0x74/0x160 kernel/entry/common.c:168
       exit_to_user_mode_prepare+0xad/0x110 kernel/entry/common.c:203
       __syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline]
       syscall_exit_to_user_mode+0x2e/0x60 kernel/entry/common.c:296
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

other info that might help us debug this:

Chain exists of:
  sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM --> rfcomm_mutex --> &d->lock

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&d->lock);
                               lock(rfcomm_mutex);
                               lock(&d->lock);
  lock(sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM);

 *** DEADLOCK ***

3 locks held by syz-executor245/5091:
 #0: ffff8880730a7a10 (&sb->s_type->i_mutex_key#9){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline]
 #0: ffff8880730a7a10 (&sb->s_type->i_mutex_key#9){+.+.}-{3:3}, at: __sock_release net/socket.c:649 [inline]
 #0: ffff8880730a7a10 (&sb->s_type->i_mutex_key#9){+.+.}-{3:3}, at: sock_close+0x93/0x260 net/socket.c:1365
 #1: ffffffff8e7e2388 (rfcomm_mutex){+.+.}-{3:3}, at: rfcomm_dlc_close+0x32/0x1c0 net/bluetooth/rfcomm/core.c:507
 #2: ffff8880151a0928 (&d->lock){+.+.}-{3:3}, at: __rfcomm_dlc_close+0x276/0x470 net/bluetooth/rfcomm/core.c:487

stack backtrace:
CPU: 0 PID: 5091 Comm: syz-executor245 Not tainted 6.2.0-rc1-syzkaller-00084-gc8451c141e07 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2d0 lib/dump_stack.c:106
 check_noncircular+0x2f9/0x3b0 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+0x184a/0x6470 kernel/locking/lockdep.c:3831
 __lock_acquire+0x1292/0x1f60 kernel/locking/lockdep.c:5055
 lock_acquire+0x1a7/0x400 kernel/locking/lockdep.c:5668
 lock_sock_nested+0x44/0xf0 net/core/sock.c:3470
 lock_sock include/net/sock.h:1725 [inline]
 rfcomm_sk_state_change+0x52/0x2f0 net/bluetooth/rfcomm/sock.c:73
 __rfcomm_dlc_close+0x2bb/0x470 net/bluetooth/rfcomm/core.c:489
 rfcomm_dlc_close+0x10d/0x1c0 net/bluetooth/rfcomm/core.c:520
 __rfcomm_sock_close+0x101/0x220 net/bluetooth/rfcomm/sock.c:220
 rfcomm_sock_shutdown+0xad/0x230 net/bluetooth/rfcomm/sock.c:907
 rfcomm_sock_release+0x55/0x120 net/bluetooth/rfcomm/sock.c:928
 __sock_release net/socket.c:650 [inline]
 sock_close+0xd7/0x260 net/socket.c:1365
 __fput+0x3ba/0x880 fs/file_table.c:320
 task_work_run+0x243/0x300 kernel/task_work.c:179
 exit_task_work include/linux/task_work.h:38 [inline]
 do_exit+0x644/0x2150 kernel/exit.c:867
 do_group_exit+0x1fd/0x2b0 kernel/exit.c:1012
 get_signal+0x1755/0x1820 kernel/signal.c:2859
 arch_do_signal_or_restart+0x8d/0x5f0 arch/x86/kernel/signal.c:306
 exit_to_user_mode_loop+0x74/0x160 kernel/entry/common.c:168
 exit_to_user_mode_prepare+0xad/0x110 kernel/entry/common.c:203
 __syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline]
 syscall_exit_to_user_mode+0x2e/0x60 kernel/entry/common.c:296
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fb6ce0544b9
Code: Unable to access opcode bytes at 0x7fb6ce05448f.
RSP: 002b:00007ffde0070378 EFLAGS: 00000246 ORIG_RAX: 000000000000002a
RAX: fffffffffffffffc RBX: 0000000000000003 RCX: 00007fb6ce0544b9
RDX: 000000000000000a RSI: 0000000020000000 RDI: 0000000000000005
RBP: 0000000000000003 R08: 0000000000000150 R09: 0000000000000150
R10: 0000000000000150 R11: 0000000000000246 R12: 00005555568332b8
R13: 0000000000000072 R14: 00007ffde00703e0 R15: 0000000000000003
 </TASK>

Crashes (5655):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets Title
ci-upstream-kasan-gce-smack-root 2022/12/31 14:44 upstream c8451c141e07 ab32d508 .config strace log report syz C [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2022/12/29 13:51 upstream 1b929c02afd3 44712fbc .config strace log report syz C [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-smack-root 2022/11/15 22:17 upstream e01d50cbd6ee 97de9cfc .config strace log report syz C [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2022/09/18 15:12 upstream a335366bad13 dd9a85ff .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-smack-root 2022/08/21 08:59 upstream 15b3f48a4339 26a13b38 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2022/07/24 00:54 upstream 70664fc10c0d 22343af4 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2022/07/06 16:33 upstream e35e5b6f695d bff65f44 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-root 2022/07/04 18:08 upstream 88084a3df167 bff65f44 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2022/07/01 05:13 upstream 1a0e93df1e10 1434eec0 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2022/06/26 21:41 upstream 0840a7914caa a371c43c .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-smack-root 2022/06/23 04:41 upstream 3abc3ae553c7 912f5df7 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2022/06/17 10:12 upstream 47700948a4ab 1719ee24 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2022/06/15 11:12 upstream 018ab4fabddd 127d1faf .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-smack-root 2022/06/01 21:19 upstream 700170bf6b4d 3666edfe .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-smack-root 2022/05/25 18:16 upstream fdaf9a5840ac 647c0e27 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2022/05/20 12:26 upstream b015dcd62b86 cb1ac2e7 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2022/05/20 05:32 upstream b015dcd62b86 cb1ac2e7 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2022/05/18 10:51 upstream 210e04ff7681 744a39e2 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2022/05/17 21:05 upstream 42226c989789 744a39e2 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2022/05/17 18:58 upstream 42226c989789 744a39e2 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2022/05/17 17:45 upstream 42226c989789 744a39e2 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2022/05/17 12:32 upstream 42226c989789 744a39e2 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-smack-root 2022/05/17 09:56 upstream 42226c989789 744a39e2 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2022/05/15 08:16 upstream 2fe1020d73ca 744a39e2 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2022/05/13 19:52 upstream f3f19f939c11 107f6434 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2022/05/13 18:50 upstream f3f19f939c11 107f6434 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2022/05/13 00:04 upstream 0ac824f379fb 9ad6612a .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-root 2022/05/12 07:42 upstream feb9c5e19e91 beb0b407 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2022/05/11 13:22 upstream feb9c5e19e91 8d7b3b67 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2022/05/11 11:35 upstream feb9c5e19e91 8d7b3b67 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2022/05/11 09:00 upstream feb9c5e19e91 8d7b3b67 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2022/05/11 07:54 upstream feb9c5e19e91 8d7b3b67 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2022/05/11 05:52 upstream feb9c5e19e91 8d7b3b67 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-smack-root 2021/09/09 20:55 upstream a3fa7a101dcf e2776ee4 .config console log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-linux-next-kasan-gce-root 2022/11/19 07:14 linux-next 15f3bff12cf6 5bb70014 .config strace log report syz C [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-linux-next-kasan-gce-root 2022/08/11 09:52 linux-next 6c8f479764eb a6201f11 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-linux-next-kasan-gce-root 2022/06/23 19:43 linux-next 08897940f458 912f5df7 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-linux-next-kasan-gce-root 2022/05/28 02:46 linux-next d3fde8ff50ab a46af346 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-linux-next-kasan-gce-root 2022/05/20 12:29 linux-next 3f7bdc402fb0 cb1ac2e7 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-linux-next-kasan-gce-root 2022/05/15 22:34 linux-next 1e1b28b936ae 744a39e2 .config strace log report syz C possible deadlock in rfcomm_sk_state_change
ci-upstream-gce-arm64 2022/10/09 23:01 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] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-root 2023/02/01 16:55 upstream c0b67534c95c 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2023/02/01 01:17 upstream 58706f7fb045 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-root 2023/01/31 06:12 upstream 22b8077d0fce 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-root 2023/01/31 03:12 upstream 22b8077d0fce 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-root 2023/01/30 15:32 upstream 6d796c50f84c 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-root 2023/01/30 01:19 upstream ab072681eabe 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-root 2023/01/29 23:48 upstream ab072681eabe 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-root 2023/01/29 15:55 upstream c96618275234 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-smack-root 2023/01/29 07:25 upstream c96618275234 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-root 2023/01/28 19:05 upstream 5af6ce704936 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2023/01/28 02:44 upstream 83abd4d4c4be 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-root 2023/01/28 00:37 upstream 83abd4d4c4be 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-selinux-root 2023/01/27 22:05 upstream 83abd4d4c4be 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-smack-root 2023/01/22 23:00 upstream 2241ab53cbb5 559a440a .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-smack-root 2023/01/20 06:25 upstream d368967cb103 559a440a .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-root 2023/01/19 19:51 upstream 081edded9b38 1b826a2f .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-root 2023/01/19 14:50 upstream 7287904c8771 1b826a2f .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-root 2023/01/19 11:16 upstream 7287904c8771 7374c4e5 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-root 2023/01/19 03:17 upstream 7287904c8771 42660d9e .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-qemu-upstream 2023/01/18 13:00 upstream c1649ec55708 4620c2d9 .config console log report info possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-root 2023/01/18 10:51 upstream c1649ec55708 42660d9e .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-root 2023/01/18 08:58 upstream c1649ec55708 42660d9e .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-qemu-upstream 2023/01/18 00:51 upstream c1649ec55708 42660d9e .config console log report info possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-root 2023/01/17 22:25 upstream 6e50979a9c87 aedf5331 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-qemu-upstream 2023/01/17 11:19 upstream 6e50979a9c87 aedf5331 .config console log report info possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-root 2023/01/17 08:21 upstream d532dd102151 a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-root 2023/01/17 02:45 upstream d532dd102151 a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-kasan-gce-root 2021/09/09 05:05 upstream 730bf31b8fc8 e2776ee4 .config console log report info possible deadlock in rfcomm_sk_state_change
ci-qemu-upstream-386 2023/01/15 17:16 upstream f0f70ddb8f3b a63719e7 .config console log report info possible deadlock in rfcomm_sk_state_change
ci-upstream-net-this-kasan-gce 2023/01/15 00:55 net a22b7388d658 a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-net-kasan-gce 2023/01/29 08:46 net-next 70eb3911d80f 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-net-kasan-gce 2023/01/18 22:06 net-next c4791b3196bf 42660d9e .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-net-kasan-gce 2023/01/16 13:10 net-next 5129bd8e8840 a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-linux-next-kasan-gce-root 2023/01/27 16:54 linux-next e2f86c02fdc9 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-linux-next-kasan-gce-root 2023/01/16 18:59 linux-next c12e2e5b76b2 a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-gce-arm64 2023/01/23 16:33 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci edb2f0dc90f2 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-gce-arm64 2023/01/23 15:10 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci edb2f0dc90f2 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-gce-arm64 2023/01/23 11:31 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci edb2f0dc90f2 44388686 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-gce-arm64 2023/01/23 07:27 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci edb2f0dc90f2 44388686 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-gce-arm64 2023/01/22 20:43 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci edb2f0dc90f2 559a440a .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-gce-arm64 2023/01/21 11:39 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci edb2f0dc90f2 559a440a .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-gce-arm64 2023/01/21 09:07 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci edb2f0dc90f2 559a440a .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-gce-arm64 2023/01/20 20:43 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci de8041bf6ca8 559a440a .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-gce-arm64 2023/01/20 19:19 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci de8041bf6ca8 559a440a .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-gce-arm64 2023/01/20 04:11 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 9598c377d828 559a440a .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-gce-arm64 2023/01/19 13:30 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 9598c377d828 1b826a2f .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-gce-arm64 2023/01/19 12:35 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 9598c377d828 1b826a2f .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-gce-arm64 2023/01/18 17:23 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 9598c377d828 42660d9e .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-gce-arm64 2023/01/18 07:40 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 9598c377d828 42660d9e .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-gce-arm64 2023/01/18 06:31 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 9598c377d828 42660d9e .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-gce-arm64 2023/01/17 18:59 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 9598c377d828 aedf5331 .config console log report info [disk image] [vmlinux] [kernel image] possible deadlock in rfcomm_sk_state_change
ci-upstream-gce-arm64 2023/01/17 15:28 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] possible deadlock in rfcomm_sk_state_change
ci-upstream-gce-arm64 2023/01/17 13:04 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] possible deadlock in rfcomm_sk_state_change
ci-upstream-gce-arm64 2023/01/17 10:24 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] possible deadlock in rfcomm_sk_state_change
* Struck through repros no longer work on HEAD.