syzbot


possible deadlock in rfcomm_sk_state_change

Status: upstream: reported C repro on 2021/09/13 05:15
Subsystems: bluetooth
[Documentation on labels]
Reported-by: syzbot+d7ce59b06b3eb14fd218@syzkaller.appspotmail.com
First crash: 922d, last: 25m
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 (14)
Title Replies (including bot) Last reply
[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] 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:lts-only C unreliable 176 2d03h 361d 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 321 17h07m 361d 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.8.0-syzkaller-08951-gfe46a7dd189e #0 Not tainted
------------------------------------------------------
syz-executor291/5092 is trying to acquire lock:
ffff88801b2b7258 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1671 [inline]
ffff88801b2b7258 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: rfcomm_sk_state_change+0x6d/0x3b0 net/bluetooth/rfcomm/sock.c:73

but task is already holding lock:
ffff88802360f928 (&d->lock){+.+.}-{3:3}, at: __rfcomm_dlc_close+0x235/0x720 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: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+0xb0/0x270 net/socket.c:659
       sock_close+0x1c/0x30 net/socket.c:1421
       __fput+0x270/0xb80 fs/file_table.c:422
       task_work_run+0x14e/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

-> #2 (rfcomm_mutex){+.+.}-{3:3}:
       __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+0x116/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+0x193/0x220 fs/ioctl.c:890
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0xd2/0x260 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x6d/0x75

-> #1 (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+0x116/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+0x193/0x220 fs/ioctl.c:890
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0xd2/0x260 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x6d/0x75

-> #0 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}:
       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
       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+0x28c/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+0xb0/0x270 net/socket.c:659
       sock_close+0x1c/0x30 net/socket.c:1421
       __fput+0x270/0xb80 fs/file_table.c:422
       task_work_run+0x14e/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

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-executor291/5092:
 #0: ffff888076e33e10 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:793 [inline]
 #0: ffff888076e33e10 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: __sock_release+0x86/0x270 net/socket.c:658
 #1: ffffffff8f57f3a8 (rfcomm_mutex){+.+.}-{3:3}, at: rfcomm_dlc_close+0x33/0x240 net/bluetooth/rfcomm/core.c:511
 #2: ffff88802360f928 (&d->lock){+.+.}-{3:3}, at: __rfcomm_dlc_close+0x235/0x720 net/bluetooth/rfcomm/core.c:491

stack backtrace:
CPU: 0 PID: 5092 Comm: syz-executor291 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
 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+0x28c/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+0xb0/0x270 net/socket.c:659
 sock_close+0x1c/0x30 net/socket.c:1421
 __fput+0x270/0xb80 fs/file_table.c:422
 task_work_run+0x14e/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
RIP: 0033:0x7fe21fb10f79
Code: Unable to access opcode bytes at 0x7fe21fb10f4f.
RSP: 002b:00007ffd83e8a108 EFLAGS: 00000246 ORIG_RAX: 000000000000002a
RAX: fffffffffffffffc RBX: 0000000000000000 RCX: 00007fe21fb10f79
RDX: 000000000000000a RSI: 0000000020000000 RDI: 0000000000000004
RBP: 00000000000f4240 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00005555699a9370
R13: 0000000000000004 R14: 00007ffd83e8a180 R15: 00007ffd83e8a170
 </TASK>

Crashes (18077):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/03/17 20:53 upstream fe46a7dd189e d615901c .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_sk_state_change
2024/03/17 10:08 upstream fe46a7dd189e d615901c .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in rfcomm_sk_state_change
2024/03/10 14:00 upstream 005f6f34bd47 6ee49f2e .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2024/03/02 19:52 upstream 5ad3cb0ed525 25905f5d .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_sk_state_change
2024/02/29 10:08 upstream e326df53af00 352ab904 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2024/02/29 09:30 upstream e326df53af00 352ab904 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2024/02/27 14:53 upstream 45ec2f5f6ed3 05e69c83 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in rfcomm_sk_state_change
2024/02/14 19:33 upstream 7e90b5c295ec 6a8ec742 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2024/01/28 16:18 upstream 8a696a29c690 cc4a4020 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in rfcomm_sk_state_change
2024/01/07 13:33 upstream 52b1853b080a d0304e9c .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in rfcomm_sk_state_change
2023/12/30 13:00 upstream f016f7547aee fb427a07 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in rfcomm_sk_state_change
2023/12/27 06:05 upstream fbafc3e621c3 fb427a07 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in rfcomm_sk_state_change
2023/12/26 10:39 upstream fbafc3e621c3 fb427a07 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_sk_state_change
2023/12/25 18:48 upstream 861deac3b092 fb427a07 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2023/12/18 19:16 upstream ceb6a6f023fd 3222d10c .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in rfcomm_sk_state_change
2023/12/18 18:41 upstream ceb6a6f023fd 3222d10c .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in rfcomm_sk_state_change
2023/12/14 20:25 upstream 5bd7ef53ffe5 3222d10c .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2023/12/06 01:21 upstream bee0e7762ad2 f819d6f7 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2023/12/04 17:15 upstream 33cc938e65a9 f819d6f7 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in rfcomm_sk_state_change
2023/12/02 23:48 upstream 815fb87b7530 f819d6f7 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_sk_state_change
2023/12/02 14:55 upstream 815fb87b7530 f819d6f7 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-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
2024/03/16 14:29 net ea80e3ed09ab d615901c .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/02/28 20:15 net ed2c0e4cb693 d367cbe5 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/02/26 20:54 net 1a825e4cdf45 edd6a5e9 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/01/20 18:20 net dbc153fd3c14 9bd8dcda .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/12/25 15:44 net dff90e4a092b fb427a07 .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/12/19 23:15 net 3dc5d4454545 3ad490ea .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/16 10:24 net-next 237bb5f7f7f5 d615901c .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/02/28 20:14 net-next 4440873f3655 d367cbe5 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/02/26 20:51 net-next 5f6000aa24b9 edd6a5e9 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/01/20 18:20 net-next 736b5545d39c 9bd8dcda .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/25 19:25 net-next e9301af385e7 fb427a07 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/01/27 06:28 linux-next 01af33cc9894 cc4a4020 .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
2024/03/16 10:01 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 707081b61156 d615901c .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2024/03/08 01:53 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 707081b61156 2b789849 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2024/03/07 05:06 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 9910665503b3 f39a7eed .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2024/01/20 23:27 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 0802e17d9aca 9bd8dcda .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2024/01/18 17:50 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 0802e17d9aca 239abf84 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2023/12/25 22:00 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci aafe7ad77b91 fb427a07 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2023/12/23 05:29 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci aafe7ad77b91 fb427a07 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2023/12/07 02:22 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci d46efae31672 e3299f55 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2023/11/29 18:17 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2cc14f52aeb7 6e78f9ce .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2024/03/15 20:25 upstream fe46a7dd189e d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2024/02/25 00:23 upstream f2e367d6ad3b 8d446f15 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in rfcomm_sk_state_change
2024/01/31 07:22 upstream 861c0981648f 373b66cd .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in rfcomm_sk_state_change
2024/02/13 08:07 upstream c664e16bb1ba 77b23aa1 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 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
2024/03/18 21:52 net 35c3e2791756 baa80228 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/17 05:57 net ea80e3ed09ab d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/17 02:41 net ea80e3ed09ab d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/17 00:31 net ea80e3ed09ab d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/16 16:33 net ea80e3ed09ab d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/15 22:01 net ea80e3ed09ab d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/19 10:11 net-next 237bb5f7f7f5 baa80228 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/19 08:12 net-next 237bb5f7f7f5 baa80228 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/19 06:49 net-next 237bb5f7f7f5 baa80228 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/19 05:29 net-next 237bb5f7f7f5 baa80228 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/19 04:14 net-next 237bb5f7f7f5 baa80228 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/19 03:01 net-next 237bb5f7f7f5 baa80228 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/19 01:17 net-next 237bb5f7f7f5 baa80228 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/18 23:44 net-next 237bb5f7f7f5 baa80228 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/18 16:29 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/18 15:17 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/18 13:49 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/18 12:40 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/18 12:31 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/18 11:13 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/18 10:10 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/18 09:05 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/18 06:37 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/18 05:40 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/18 03:55 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/18 02:53 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/18 01:38 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/18 00:10 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/17 22:26 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/17 20:39 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/17 20:31 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/17 19:10 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/17 17:56 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/17 16:53 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/17 15:33 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/17 13:40 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/17 12:16 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/17 09:33 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/17 06:58 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/17 04:19 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/17 03:05 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/16 23:02 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/16 21:37 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/16 17:41 net-next 237bb5f7f7f5 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/03/15 16:58 net-next 19c5c04d3178 d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2024/02/12 07:48 linux-next ae00c445390b 77b23aa1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2024/03/18 18:09 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 707081b61156 baa80228 .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.