syzbot


possible deadlock in rfcomm_sk_state_change

Status: upstream: reported C repro on 2021/09/13 05:15
Labels: bluetooth (incorrect?)
Reported-by: syzbot+d7ce59b06b3eb14fd218@syzkaller.appspotmail.com
First crash: 626d, last: now

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
Discussions (4)
Title Replies (including bot) Last reply
[syzbot] Monthly bluetooth report (Apr 2023) 0 (1) 2023/04/30 08:00
[syzbot] Monthly bluetooth report 0 (1) 2023/03/29 10:03
[PATCH v3] Bluetooth: Fix possible deadlock in rfcomm_sk_state_change 2 (2) 2023/01/11 20:10
[syzbot] possible deadlock in rfcomm_sk_state_change 0 (1) 2021/09/13 05:15
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 possible deadlock in rfcomm_sk_state_change origin:upstream C 30 1d01h 65d 0/3 upstream: reported C repro on 2023/03/24 09:07
linux-5.15 possible deadlock in rfcomm_sk_state_change origin:upstream C 61 1d06h 65d 0/3 upstream: reported C repro on 2023/03/24 00:34
Last patch testing requests (2)
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.4.0-rc3-syzkaller-00008-gae8373a5add4 #0 Not tainted
------------------------------------------------------
syz-executor231/5029 is trying to acquire lock:
ffff88802ab30130 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1697 [inline]
ffff88802ab30130 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: rfcomm_sk_state_change+0x6d/0x3a0 net/bluetooth/rfcomm/sock.c:73

but task is already holding lock:
ffff888021795928 (&d->lock){+.+.}-{3:3}, at: __rfcomm_dlc_close+0x15d/0x890 net/bluetooth/rfcomm/core.c:491

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (&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:1397
       __fput+0x27c/0xa90 fs/file_table.c:321
       task_work_run+0x16f/0x270 kernel/task_work.c:179
       exit_task_work include/linux/task_work.h:38 [inline]
       do_exit+0xad3/0x2960 kernel/exit.c:871
       do_group_exit+0xd4/0x2a0 kernel/exit.c:1021
       get_signal+0x2315/0x25b0 kernel/signal.c:2874
       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+0x11f/0x240 kernel/entry/common.c:204
       __syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
       syscall_exit_to_user_mode+0x1d/0x50 kernel/entry/common.c:297
       do_syscall_64+0x46/0xb0 arch/x86/entry/common.c:86
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #2 (rfcomm_mutex){+.+.}-{3:3}:
       __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:1201
       sock_ioctl+0x1f8/0x680 net/socket.c:1318
       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

-> #1 (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:1201
       sock_ioctl+0x1f8/0x680 net/socket.c:1318
       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

-> #0 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}:
       check_prev_add kernel/locking/lockdep.c:3108 [inline]
       check_prevs_add kernel/locking/lockdep.c:3227 [inline]
       validate_chain kernel/locking/lockdep.c:3842 [inline]
       __lock_acquire+0x2f21/0x5df0 kernel/locking/lockdep.c:5074
       lock_acquire kernel/locking/lockdep.c:5691 [inline]
       lock_acquire+0x1b1/0x520 kernel/locking/lockdep.c:5656
       lock_sock_nested+0x3a/0xf0 net/core/sock.c:3469
       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:1397
       __fput+0x27c/0xa90 fs/file_table.c:321
       task_work_run+0x16f/0x270 kernel/task_work.c:179
       exit_task_work include/linux/task_work.h:38 [inline]
       do_exit+0xad3/0x2960 kernel/exit.c:871
       do_group_exit+0xd4/0x2a0 kernel/exit.c:1021
       get_signal+0x2315/0x25b0 kernel/signal.c:2874
       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+0x11f/0x240 kernel/entry/common.c:204
       __syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
       syscall_exit_to_user_mode+0x1d/0x50 kernel/entry/common.c:297
       do_syscall_64+0x46/0xb0 arch/x86/entry/common.c:86
       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-executor231/5029:
 #0: ffff88807694d010 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:775 [inline]
 #0: ffff88807694d010 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: __sock_release+0x86/0x290 net/socket.c:652
 #1: ffffffff8e371088 (rfcomm_mutex){+.+.}-{3:3}, at: rfcomm_dlc_close+0x33/0x240 net/bluetooth/rfcomm/core.c:511
 #2: ffff888021795928 (&d->lock){+.+.}-{3:3}, at: __rfcomm_dlc_close+0x15d/0x890 net/bluetooth/rfcomm/core.c:491

stack backtrace:
CPU: 0 PID: 5029 Comm: syz-executor231 Not tainted 6.4.0-rc3-syzkaller-00008-gae8373a5add4 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/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:2188
 check_prev_add kernel/locking/lockdep.c:3108 [inline]
 check_prevs_add kernel/locking/lockdep.c:3227 [inline]
 validate_chain kernel/locking/lockdep.c:3842 [inline]
 __lock_acquire+0x2f21/0x5df0 kernel/locking/lockdep.c:5074
 lock_acquire kernel/locking/lockdep.c:5691 [inline]
 lock_acquire+0x1b1/0x520 kernel/locking/lockdep.c:5656
 lock_sock_nested+0x3a/0xf0 net/core/sock.c:3469
 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:1397
 __fput+0x27c/0xa90 fs/file_table.c:321
 task_work_run+0x16f/0x270 kernel/task_work.c:179
 exit_task_work include/linux/task_work.h:38 [inline]
 do_exit+0xad3/0x2960 kernel/exit.c:871
 do_group_exit+0xd4/0x2a0 kernel/exit.c:1021
 get_signal+0x2315/0x25b0 kernel/signal.c:2874
 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+0x11f/0x240 kernel/entry/common.c:204
 __syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
 syscall_exit_to_user_mode+0x1d/0x50 kernel/entry/common.c:297
 do_syscall_64+0x46/0xb0 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f7f016d7599
Code: Unable to access opcode bytes at 0x7f7f016d756f.
RSP: 002b:00007ffe2870a098 EFLAGS: 00000246 ORIG_RAX: 000000000000002a
RAX: fffffffffffffffc RBX: 00000000000f4240 RCX: 00007f7f016d7599
RDX: 000000000000000a RSI: 0000000020000180 RDI: 0000000000000003
RBP: 0000000000000000 R08: 0000000000000150 R09: 0000000000000150
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffe2870a140
R13: 00007ffe2870a110 R14: 00007ffe2870a100 R15: 0000000000000003
 </TASK>

Crashes (6448):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets Manager Title
2023/05/23 23:50 upstream ae8373a5add4 4bce1a3e .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2023/05/07 06:06 upstream fc4354c6e5c2 90c93c40 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2023/05/07 05:36 upstream fc4354c6e5c2 90c93c40 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2023/02/28 12:00 upstream 982818426a0f 95aee97a .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2022/12/31 14:44 upstream c8451c141e07 ab32d508 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in rfcomm_sk_state_change
2022/12/29 13:51 upstream 1b929c02afd3 44712fbc .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_sk_state_change
2022/11/15 22:17 upstream e01d50cbd6ee 97de9cfc .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in rfcomm_sk_state_change
2022/09/18 15:12 upstream a335366bad13 dd9a85ff .config strace log report syz C ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_sk_state_change
2022/08/21 08:59 upstream 15b3f48a4339 26a13b38 .config strace log report syz C ci-upstream-kasan-gce-smack-root possible deadlock in rfcomm_sk_state_change
2022/07/24 00:54 upstream 70664fc10c0d 22343af4 .config strace log report syz C ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_sk_state_change
2022/07/06 16:33 upstream e35e5b6f695d bff65f44 .config strace log report syz C ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_sk_state_change
2022/07/04 18:08 upstream 88084a3df167 bff65f44 .config strace log report syz C ci-upstream-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2022/07/01 05:13 upstream 1a0e93df1e10 1434eec0 .config strace log report syz C ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_sk_state_change
2022/06/26 21:41 upstream 0840a7914caa a371c43c .config strace log report syz C ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_sk_state_change
2022/06/23 04:41 upstream 3abc3ae553c7 912f5df7 .config strace log report syz C ci-upstream-kasan-gce-smack-root possible deadlock in rfcomm_sk_state_change
2022/06/17 10:12 upstream 47700948a4ab 1719ee24 .config strace log report syz C ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_sk_state_change
2022/06/15 11:12 upstream 018ab4fabddd 127d1faf .config strace log report syz C ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_sk_state_change
2022/06/01 21:19 upstream 700170bf6b4d 3666edfe .config strace log report syz C ci-upstream-kasan-gce-smack-root possible deadlock in rfcomm_sk_state_change
2022/05/25 18:16 upstream fdaf9a5840ac 647c0e27 .config strace log report syz C ci-upstream-kasan-gce-smack-root possible deadlock in rfcomm_sk_state_change
2021/09/09 20:55 upstream a3fa7a101dcf e2776ee4 .config console log report syz C ci-upstream-kasan-gce-smack-root possible deadlock in rfcomm_sk_state_change
2023/05/26 08:24 net ad42a35bdfc6 b40ef614 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/03/30 10:11 net 8c495270845d f325deb0 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/03/23 22:45 net b1de5c78ebe9 f94b4a29 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/02/04 20:04 net-old a05e7a67986c be607b78 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/02/04 18:15 net-old a05e7a67986c be607b78 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/26 06:31 net-next 657d42cf5df6 b40ef614 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/03/30 08:49 net-next 615927f1a487 f325deb0 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/03/23 23:28 net-next fcb3a4653bc5 f94b4a29 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/02/04 18:51 net-next-old 042b7858d50f be607b78 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/02/04 17:57 net-next-old 042b7858d50f be607b78 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/02/27 19:19 linux-next 7f7a8831520f e792ae78 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2022/11/19 07:14 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 rfcomm_sk_state_change
2022/08/11 09:52 linux-next 6c8f479764eb a6201f11 .config strace log report syz C ci-upstream-linux-next-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2022/06/23 19:43 linux-next 08897940f458 912f5df7 .config strace log report syz C ci-upstream-linux-next-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2022/05/28 02:46 linux-next d3fde8ff50ab a46af346 .config strace log report syz C ci-upstream-linux-next-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2023/05/26 03:08 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci f1fcbaa18b28 0513b3e6 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2023/03/30 08:03 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 59caa87f9dfb f325deb0 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2023/03/23 23:36 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci fe15c26ee26e f94b4a29 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2023/02/28 12:50 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2ebd1fbb946d 95aee97a .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2023/02/27 19:52 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2ebd1fbb946d e792ae78 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2023/02/04 21:21 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci ca72d58361ee be607b78 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2023/02/04 17:34 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci ca72d58361ee be607b78 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
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] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2023/05/28 05:18 upstream 4e893b5aa4ac cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2023/05/28 01:35 upstream 4e893b5aa4ac cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_sk_state_change
2023/05/27 02:06 upstream 91a304340a22 cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in rfcomm_sk_state_change
2023/05/26 20:03 upstream 0d85b27b0cc6 cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2023/05/26 00:04 upstream eb03e3181354 0513b3e6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2023/05/25 20:18 upstream eb03e3181354 0513b3e6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2023/05/24 04:39 upstream 27e462c8fad4 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2023/05/22 09:48 upstream 44c026a73be8 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2023/05/22 00:55 upstream e2065b8c1b01 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in rfcomm_sk_state_change
2023/05/19 09:13 upstream 2d1bcbc6cd70 3bb7af1d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_sk_state_change
2023/04/30 22:57 upstream 58390c8ce1bd 62df2017 .config console log report info ci-qemu-upstream possible deadlock in rfcomm_sk_state_change
2021/09/09 05:05 upstream 730bf31b8fc8 e2776ee4 .config console log report info ci-upstream-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2023/05/27 14:41 upstream 49572d536129 cf184559 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in rfcomm_sk_state_change
2023/05/23 13:44 upstream ae8373a5add4 4bce1a3e .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in rfcomm_sk_state_change
2023/05/27 11:51 net 9b9e46aa0727 cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/26 05:35 net ad42a35bdfc6 b40ef614 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/26 04:13 net ad42a35bdfc6 b40ef614 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/26 02:33 net ad42a35bdfc6 0513b3e6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/25 13:34 net aa015a204b60 0513b3e6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/25 08:26 net aa015a204b60 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/24 17:30 net 878ecb0897f4 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/24 15:25 net 878ecb0897f4 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/24 09:28 net 7e7b3b097a9d 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/24 08:12 net 7e7b3b097a9d 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/23 19:25 net 3632679d9e4f 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/23 17:33 net 3632679d9e4f 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/23 06:20 net 18c40a1cc1d9 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/23 04:35 net 18c40a1cc1d9 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/23 01:53 net 6ca328e985cd 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/22 23:43 net 6ca328e985cd 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/22 22:29 net 6ca328e985cd 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/22 14:15 net 6ca328e985cd 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/22 13:12 net 6ca328e985cd 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/22 11:09 net 6ca328e985cd 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/28 10:48 net-next 75455b906d82 cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/28 08:30 net-next 75455b906d82 cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/27 08:28 net-next 75455b906d82 cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/27 06:59 net-next 75455b906d82 cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/26 18:22 net-next 4781e965e655 cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/26 01:34 net-next 657d42cf5df6 0513b3e6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/25 11:23 net-next 8a5ad2ea6b87 0513b3e6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/25 05:34 net-next 8a5ad2ea6b87 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/24 15:52 net-next 41a45ea49d3a 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/24 07:09 net-next 57910a47ffe9 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/24 05:46 net-next 57910a47ffe9 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/24 03:01 net-next b2e3406a38f0 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/23 15:36 net-next b2e3406a38f0 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/23 08:44 net-next d49b9b07725f 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/23 03:05 net-next d49b9b07725f 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/22 03:28 net-next dcbe4ea1985d 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/21 22:28 net-next dcbe4ea1985d 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/21 19:50 net-next dcbe4ea1985d 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/05/25 18:39 linux-next 715abedee4cd 0513b3e6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2023/05/25 17:35 linux-next 715abedee4cd 0513b3e6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2023/05/24 19:38 linux-next 715abedee4cd 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2023/05/27 20:27 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci eb0f1697d729 cf184559 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
* Struck through repros no longer work on HEAD.