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: 818d, last: 44m
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 (11)
Title Replies (including bot) Last reply
[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 135 21h59m 257d 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 258 5h22m 257d 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.7.0-rc4-syzkaller-00009-gbee0e7762ad2 #0 Not tainted
------------------------------------------------------
syz-executor178/5100 is trying to acquire lock:
ffff888073cfc130 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1720 [inline]
ffff888073cfc130 (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:
ffff8880297ad128 (&d->lock){+.+.}-{3:3}, at: __rfcomm_dlc_close+0x231/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:603 [inline]
       __mutex_lock+0x175/0x9d0 kernel/locking/mutex.c:747
       __rfcomm_dlc_close+0x231/0x720 net/bluetooth/rfcomm/core.c:491
       rfcomm_dlc_close+0x1e7/0x240 net/bluetooth/rfcomm/core.c:524
       __rfcomm_sock_close+0xa7/0x230 net/bluetooth/rfcomm/sock.c:220
       rfcomm_sock_shutdown+0xd1/0x230 net/bluetooth/rfcomm/sock.c:905
       rfcomm_sock_release+0x5d/0x140 net/bluetooth/rfcomm/sock.c:926
       __sock_release+0xae/0x260 net/socket.c:659
       sock_close+0x1c/0x20 net/socket.c:1419
       __fput+0x270/0xbb0 fs/file_table.c:394
       task_work_run+0x14d/0x240 kernel/task_work.c:180
       exit_task_work include/linux/task_work.h:38 [inline]
       do_exit+0xa92/0x2ae0 kernel/exit.c:871
       do_group_exit+0xd4/0x2a0 kernel/exit.c:1021
       get_signal+0x23be/0x2790 kernel/signal.c:2904
       arch_do_signal_or_restart+0x90/0x7f0 arch/x86/kernel/signal.c:309
       exit_to_user_mode_loop kernel/entry/common.c:168 [inline]
       exit_to_user_mode_prepare+0x121/0x240 kernel/entry/common.c:204
       __syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline]
       syscall_exit_to_user_mode+0x1e/0x60 kernel/entry/common.c:296
       do_syscall_64+0x4d/0x110 arch/x86/entry/common.c:88
       entry_SYSCALL_64_after_hwframe+0x63/0x6b

-> #2 (rfcomm_mutex){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x175/0x9d0 kernel/locking/mutex.c:747
       rfcomm_dlc_exists+0x5b/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+0x999/0x1c50 net/bluetooth/rfcomm/tty.c:587
       rfcomm_sock_ioctl+0xb0/0xe0 net/bluetooth/rfcomm/sock.c:873
       sock_do_ioctl+0x113/0x270 net/socket.c:1220
       sock_ioctl+0x22e/0x6b0 net/socket.c:1339
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:871 [inline]
       __se_sys_ioctl fs/ioctl.c:857 [inline]
       __x64_sys_ioctl+0x18f/0x210 fs/ioctl.c:857
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x40/0x110 arch/x86/entry/common.c:82
       entry_SYSCALL_64_after_hwframe+0x63/0x6b

-> #1 (rfcomm_ioctl_mutex){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x175/0x9d0 kernel/locking/mutex.c:747
       rfcomm_create_dev net/bluetooth/rfcomm/tty.c:484 [inline]
       rfcomm_dev_ioctl+0x8b9/0x1c50 net/bluetooth/rfcomm/tty.c:587
       rfcomm_sock_ioctl+0xb0/0xe0 net/bluetooth/rfcomm/sock.c:873
       sock_do_ioctl+0x113/0x270 net/socket.c:1220
       sock_ioctl+0x22e/0x6b0 net/socket.c:1339
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:871 [inline]
       __se_sys_ioctl fs/ioctl.c:857 [inline]
       __x64_sys_ioctl+0x18f/0x210 fs/ioctl.c:857
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x40/0x110 arch/x86/entry/common.c:82
       entry_SYSCALL_64_after_hwframe+0x63/0x6b

-> #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+0x2433/0x3b20 kernel/locking/lockdep.c:5137
       lock_acquire kernel/locking/lockdep.c:5754 [inline]
       lock_acquire+0x1ae/0x520 kernel/locking/lockdep.c:5719
       lock_sock_nested+0x3a/0xf0 net/core/sock.c:3519
       lock_sock include/net/sock.h:1720 [inline]
       rfcomm_sk_state_change+0x6d/0x3a0 net/bluetooth/rfcomm/sock.c:73
       __rfcomm_dlc_close+0x285/0x720 net/bluetooth/rfcomm/core.c:493
       rfcomm_dlc_close+0x1e7/0x240 net/bluetooth/rfcomm/core.c:524
       __rfcomm_sock_close+0xa7/0x230 net/bluetooth/rfcomm/sock.c:220
       rfcomm_sock_shutdown+0xd1/0x230 net/bluetooth/rfcomm/sock.c:905
       rfcomm_sock_release+0x5d/0x140 net/bluetooth/rfcomm/sock.c:926
       __sock_release+0xae/0x260 net/socket.c:659
       sock_close+0x1c/0x20 net/socket.c:1419
       __fput+0x270/0xbb0 fs/file_table.c:394
       task_work_run+0x14d/0x240 kernel/task_work.c:180
       exit_task_work include/linux/task_work.h:38 [inline]
       do_exit+0xa92/0x2ae0 kernel/exit.c:871
       do_group_exit+0xd4/0x2a0 kernel/exit.c:1021
       get_signal+0x23be/0x2790 kernel/signal.c:2904
       arch_do_signal_or_restart+0x90/0x7f0 arch/x86/kernel/signal.c:309
       exit_to_user_mode_loop kernel/entry/common.c:168 [inline]
       exit_to_user_mode_prepare+0x121/0x240 kernel/entry/common.c:204
       __syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline]
       syscall_exit_to_user_mode+0x1e/0x60 kernel/entry/common.c:296
       do_syscall_64+0x4d/0x110 arch/x86/entry/common.c:88
       entry_SYSCALL_64_after_hwframe+0x63/0x6b

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-executor178/5100:
 #0: ffff88807497d610 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:802 [inline]
 #0: ffff88807497d610 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: __sock_release+0x86/0x260 net/socket.c:658
 #1: ffffffff8ed3ac88 (rfcomm_mutex){+.+.}-{3:3}, at: rfcomm_dlc_close+0x33/0x240 net/bluetooth/rfcomm/core.c:511
 #2: ffff8880297ad128 (&d->lock){+.+.}-{3:3}, at: __rfcomm_dlc_close+0x231/0x720 net/bluetooth/rfcomm/core.c:491

stack backtrace:
CPU: 1 PID: 5100 Comm: syz-executor178 Not tainted 6.7.0-rc4-syzkaller-00009-gbee0e7762ad2 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd9/0x1b0 lib/dump_stack.c:106
 check_noncircular+0x317/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+0x2433/0x3b20 kernel/locking/lockdep.c:5137
 lock_acquire kernel/locking/lockdep.c:5754 [inline]
 lock_acquire+0x1ae/0x520 kernel/locking/lockdep.c:5719
 lock_sock_nested+0x3a/0xf0 net/core/sock.c:3519
 lock_sock include/net/sock.h:1720 [inline]
 rfcomm_sk_state_change+0x6d/0x3a0 net/bluetooth/rfcomm/sock.c:73
 __rfcomm_dlc_close+0x285/0x720 net/bluetooth/rfcomm/core.c:493
 rfcomm_dlc_close+0x1e7/0x240 net/bluetooth/rfcomm/core.c:524
 __rfcomm_sock_close+0xa7/0x230 net/bluetooth/rfcomm/sock.c:220
 rfcomm_sock_shutdown+0xd1/0x230 net/bluetooth/rfcomm/sock.c:905
 rfcomm_sock_release+0x5d/0x140 net/bluetooth/rfcomm/sock.c:926
 __sock_release+0xae/0x260 net/socket.c:659
 sock_close+0x1c/0x20 net/socket.c:1419
 __fput+0x270/0xbb0 fs/file_table.c:394
 task_work_run+0x14d/0x240 kernel/task_work.c:180
 exit_task_work include/linux/task_work.h:38 [inline]
 do_exit+0xa92/0x2ae0 kernel/exit.c:871
 do_group_exit+0xd4/0x2a0 kernel/exit.c:1021
 get_signal+0x23be/0x2790 kernel/signal.c:2904
 arch_do_signal_or_restart+0x90/0x7f0 arch/x86/kernel/signal.c:309
 exit_to_user_mode_loop kernel/entry/common.c:168 [inline]
 exit_to_user_mode_prepare+0x121/0x240 kernel/entry/common.c:204
 __syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline]
 syscall_exit_to_user_mode+0x1e/0x60 kernel/entry/common.c:296
 do_syscall_64+0x4d/0x110 arch/x86/entry/common.c:88
 entry_SYSCALL_64_after_hwframe+0x63/0x6b
RIP: 0033:0x7fa7c0511f79
Code: Unable to access opcode bytes at 0x7fa7c0511f4f.
RSP: 002b:00007ffe678679e8 EFLAGS: 00000246 ORIG_RAX: 000000000000002a
RAX: fffffffffffffffc RBX: 0000000000000000 RCX: 00007fa7c0511f79
RDX: 000000000000000a RSI: 0000000020000200 RDI: 0000000000000004
RBP: 00000000000f4240 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000555556115370
R13: 0000000000000002 R14: 00007ffe67867a60 R15: 00007ffe67867a50
 </TASK>

Crashes (14908):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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
2023/11/29 04:22 upstream df60cee26a2e 1adfb6f6 .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/11/25 17:18 upstream 0f5cc96c367f 5b429f39 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2023/11/10 06:38 upstream 4bbdb725a36b 56230772 .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/11/08 02:26 upstream 13d88ac54ddd 83211397 .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/11/03 10:00 upstream 4652b8e4f3ff c4ac074c .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/10/31 09:42 upstream 14ab6d425e80 b5729d82 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2023/10/22 16:45 upstream 1acfd2bd3f0d 361b23dc .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in rfcomm_sk_state_change
2023/10/16 23:19 upstream 58720809f527 6388bc36 .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/10/11 20:05 upstream 1c8b86a3799f 83165b57 .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/08/24 07:48 upstream a5e505a99ca7 4d7ae7ab .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2023/08/19 16:54 upstream d4ddefee5160 d216d8a0 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in rfcomm_sk_state_change
2023/08/18 23:43 upstream 0e8860d2125f d216d8a0 .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/08/18 22:20 upstream 0e8860d2125f d216d8a0 .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/08/02 10:53 upstream 5d0c230f1de8 df07ffe8 .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/08/02 10:18 upstream 5d0c230f1de8 df07ffe8 .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/07/16 13:30 upstream 831fe284d827 35d9ecc5 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-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/10/19 08:27 net 2915240eddba 342b9c55 .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/09/06 03:21 net d3287e4038ca 8bc9053e .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/08/27 21:09 net 5c905279a1b7 03d9c195 .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/08/14 05:29 net cc941e548bff 39990d51 .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/07/21 19:13 net 57f1f9dd3abe 28847498 .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/11/24 05:39 net-next aadbd27f9674 5b429f39 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/09/05 03:11 net-next bd6c11bc43c4 8bc9053e .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/08/27 21:51 net-next aa05346dad4b 03d9c195 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/08/18 18:45 net-next c2e5f4fd1148 d216d8a0 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/07/20 00:45 net-next 36395b2efe90 4547cdf9 .config strace log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/11/07 17:54 linux-next e27090b1413f 83211397 .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
2023/10/23 20:35 linux-next e8361b005d7c 989a3687 .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
2023/10/19 19:43 linux-next 4230ea146b1e 42e1d524 .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
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
2023/11/29 17:47 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
2023/11/24 00:41 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8de1e7afcc1c fc59b78e .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2023/11/21 12:46 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8de1e7afcc1c cb976f63 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2023/11/13 06:57 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8de1e7afcc1c 6d6dbf8a .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2023/10/30 20:18 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8de1e7afcc1c b5729d82 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2023/10/23 04:25 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 78124b0c1d10 361b23dc .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2023/10/16 10:00 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 249eb8f39efb 6388bc36 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2023/10/10 01:43 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 19af4a4ed414 3c53c7d9 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2023/09/18 13:59 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci fe4469582053 0b6a67ac .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2023/07/21 07:43 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci e40939bbfc68 28847498 .config console log report syz C [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in rfcomm_sk_state_change
2023/12/06 18:04 upstream bee0e7762ad2 e3299f55 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in rfcomm_sk_state_change
2023/12/01 20:02 upstream 994d5c58e50e f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in rfcomm_sk_state_change
2023/10/20 11:17 upstream ce55c22ec8b2 a42250d2 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream possible deadlock in rfcomm_sk_state_change
2023/10/19 10:43 upstream dd72f9c7e512 f62755ed .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
2023/12/06 19:43 net 3142dbf084cb e3299f55 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/06 15:41 net 3142dbf084cb e3299f55 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/06 12:12 net 58d3aade20cd f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/06 11:04 net 58d3aade20cd f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/06 08:39 net 58d3aade20cd f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/06 08:09 net 58d3aade20cd f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/06 06:00 net 58d3aade20cd f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/06 04:31 net 3c91c909f13f f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/06 03:52 net 3c91c909f13f f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/05 16:32 net 3c91c909f13f f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/05 13:27 net 6b17a597fc2f f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/05 12:21 net 6b17a597fc2f f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/05 03:33 net 6b17a597fc2f f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/05 03:18 net 6b17a597fc2f f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/04 19:49 net 79321a793945 f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/04 18:19 net 79321a793945 f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/04 14:06 net 79321a793945 f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/04 11:46 net 4b0768b6556a f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/06 21:15 net-next 074ac38d5b95 e3299f55 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/06 14:41 net-next 074ac38d5b95 e3299f55 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/06 09:43 net-next 19b707c3f23a f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/06 07:03 net-next 19b707c3f23a f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/06 02:34 net-next fb70136ded2e f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/06 00:51 net-next fb70136ded2e f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/05 23:46 net-next fb70136ded2e f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/05 22:08 net-next fb70136ded2e f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/05 19:02 net-next fb70136ded2e f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/05 17:40 net-next fb70136ded2e f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/05 17:35 net-next fb70136ded2e f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/05 15:04 net-next be5fc78a0084 f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/05 14:02 net-next be5fc78a0084 f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/05 11:18 net-next be5fc78a0084 f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/05 10:18 net-next be5fc78a0084 f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/05 09:09 net-next be5fc78a0084 f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/05 08:37 net-next be5fc78a0084 f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/05 04:46 net-next be5fc78a0084 f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/05 01:38 net-next 21f49681658d f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/05 00:37 net-next 21f49681658d f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/04 23:26 net-next 21f49681658d f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/04 21:43 net-next 21f49681658d f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/04 15:56 net-next 21f49681658d f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/04 14:32 net-next 21f49681658d f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/04 13:01 net-next 8470e4368b0f f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/04 09:42 net-next 8470e4368b0f f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/12/04 08:40 net-next 8470e4368b0f f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-kasan-gce possible deadlock in rfcomm_sk_state_change
2023/11/13 22:12 linux-next d173336e238b cb976f63 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in rfcomm_sk_state_change
* Struck through repros no longer work on HEAD.