syzbot


possible deadlock in rfcomm_sk_state_change

Status: upstream: reported C repro on 2023/03/24 00:34
Reported-by: syzbot+c64eacb8167598605d06@syzkaller.appspotmail.com
First crash: 638d, last: 68d
Fix bisection: failed (error log, bisect log)
  
Bug presence (1)
Date Name Commit Repro Result
2024/11/15 upstream (ToT) e8bdb3c8be08 C Didn't crash
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 365 64d 638d 0/3 upstream: reported C repro on 2023/03/24 09:07
upstream possible deadlock in rfcomm_sk_state_change bluetooth C done 22650 67d 1195d 28/28 fixed on 2024/11/12 23:31
Last patch testing requests (7)
Created Duration User Patch Repo Result
2024/11/11 14:17 20m retest repro linux-5.15.y OK log
2024/11/11 14:17 31m retest repro linux-5.15.y OK log
2024/11/11 14:17 1h45m retest repro linux-5.15.y OK log
2024/11/11 14:17 18m retest repro linux-5.15.y OK log
2024/11/11 03:39 20m retest repro linux-5.15.y OK log
2024/11/11 03:39 17m retest repro linux-5.15.y OK log
2024/11/11 03:39 17m retest repro linux-5.15.y OK log

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
5.15.167-syzkaller #0 Not tainted
------------------------------------------------------
syz.0.352/5268 is trying to acquire lock:
ffff88801bbc6120 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM#2){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1676 [inline]
ffff88801bbc6120 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM#2){+.+.}-{0:0}, at: rfcomm_sk_state_change+0x57/0x300 net/bluetooth/rfcomm/sock.c:73

but task is already holding lock:
ffff888062009128 (&d->lock#2){+.+.}-{3:3}, at: __rfcomm_dlc_close+0x259/0x6d0 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#2){+.+.}-{3:3}:
       lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
       __mutex_lock_common+0x1da/0x25a0 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
       __rfcomm_dev_add net/bluetooth/rfcomm/tty.c:278 [inline]
       rfcomm_dev_add net/bluetooth/rfcomm/tty.c:326 [inline]
       __rfcomm_create_dev net/bluetooth/rfcomm/tty.c:425 [inline]
       rfcomm_create_dev net/bluetooth/rfcomm/tty.c:486 [inline]
       rfcomm_dev_ioctl+0x14f8/0x2180 net/bluetooth/rfcomm/tty.c:588
       rfcomm_sock_ioctl+0x82/0xc0 net/bluetooth/rfcomm/sock.c:880
       sock_do_ioctl+0x11d/0x5a0 net/socket.c:1140
       sock_ioctl+0x47f/0x770 net/socket.c:1257
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:874 [inline]
       __se_sys_ioctl+0xf1/0x160 fs/ioctl.c:860
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #1 (rfcomm_dev_lock){+.+.}-{3:3}:
       lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
       __mutex_lock_common+0x1da/0x25a0 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
       rfcomm_dev_get+0x7d/0x380 net/bluetooth/rfcomm/tty.c:164
       rfcomm_get_dev_info net/bluetooth/rfcomm/tty.c:565 [inline]
       rfcomm_dev_ioctl+0x29d/0x2180 net/bluetooth/rfcomm/tty.c:597
       rfcomm_sock_ioctl+0x82/0xc0 net/bluetooth/rfcomm/sock.c:880
       sock_do_ioctl+0x11d/0x5a0 net/socket.c:1140
       sock_ioctl+0x47f/0x770 net/socket.c:1257
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:874 [inline]
       __se_sys_ioctl+0xf1/0x160 fs/ioctl.c:860
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #0 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM#2){+.+.}-{0:0}:
       check_prev_add kernel/locking/lockdep.c:3053 [inline]
       check_prevs_add kernel/locking/lockdep.c:3172 [inline]
       validate_chain+0x1649/0x5930 kernel/locking/lockdep.c:3788
       __lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5012
       lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
       lock_sock_nested+0x44/0x100 net/core/sock.c:3250
       lock_sock include/net/sock.h:1676 [inline]
       rfcomm_sk_state_change+0x57/0x300 net/bluetooth/rfcomm/sock.c:73
       __rfcomm_dlc_close+0x2b2/0x6d0 net/bluetooth/rfcomm/core.c:489
       rfcomm_dlc_close+0xed/0x180 net/bluetooth/rfcomm/core.c:520
       __rfcomm_sock_close+0x104/0x220 net/bluetooth/rfcomm/sock.c:220
       rfcomm_sock_shutdown+0xb4/0x230 net/bluetooth/rfcomm/sock.c:912
       __sys_shutdown_sock net/socket.c:2270 [inline]
       __sys_shutdown net/socket.c:2282 [inline]
       __do_sys_shutdown net/socket.c:2290 [inline]
       __se_sys_shutdown+0x147/0x1a0 net/socket.c:2288
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

other info that might help us debug this:

Chain exists of:
  sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM#2 --> rfcomm_dev_lock --> &d->lock#2

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&d->lock#2);
                               lock(rfcomm_dev_lock);
                               lock(&d->lock#2);
  lock(sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM#2);

 *** DEADLOCK ***

2 locks held by syz.0.352/5268:
 #0: ffffffff8db9a628 (rfcomm_mutex){+.+.}-{3:3}, at: rfcomm_dlc_close+0x37/0x180 net/bluetooth/rfcomm/core.c:507
 #1: ffff888062009128 (&d->lock#2){+.+.}-{3:3}, at: __rfcomm_dlc_close+0x259/0x6d0 net/bluetooth/rfcomm/core.c:487

stack backtrace:
CPU: 1 PID: 5268 Comm: syz.0.352 Not tainted 5.15.167-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2d0 lib/dump_stack.c:106
 check_noncircular+0x2f8/0x3b0 kernel/locking/lockdep.c:2133
 check_prev_add kernel/locking/lockdep.c:3053 [inline]
 check_prevs_add kernel/locking/lockdep.c:3172 [inline]
 validate_chain+0x1649/0x5930 kernel/locking/lockdep.c:3788
 __lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5012
 lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
 lock_sock_nested+0x44/0x100 net/core/sock.c:3250
 lock_sock include/net/sock.h:1676 [inline]
 rfcomm_sk_state_change+0x57/0x300 net/bluetooth/rfcomm/sock.c:73
 __rfcomm_dlc_close+0x2b2/0x6d0 net/bluetooth/rfcomm/core.c:489
 rfcomm_dlc_close+0xed/0x180 net/bluetooth/rfcomm/core.c:520
 __rfcomm_sock_close+0x104/0x220 net/bluetooth/rfcomm/sock.c:220
 rfcomm_sock_shutdown+0xb4/0x230 net/bluetooth/rfcomm/sock.c:912
 __sys_shutdown_sock net/socket.c:2270 [inline]
 __sys_shutdown net/socket.c:2282 [inline]
 __do_sys_shutdown net/socket.c:2290 [inline]
 __se_sys_shutdown+0x147/0x1a0 net/socket.c:2288
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f780494eff9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f7802da6038 EFLAGS: 00000246 ORIG_RAX: 0000000000000030
RAX: ffffffffffffffda RBX: 00007f7804b07058 RCX: 00007f780494eff9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000004
RBP: 00007f78049c1296 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007f7804b07058 R15: 00007ffe7c7c31c8
 </TASK>

Crashes (458):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/10/14 03:44 linux-5.15.y 3a5928702e71 084d8178 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/10/10 14:34 linux-5.15.y 3a5928702e71 0278d004 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/10/05 23:54 linux-5.15.y 3a5928702e71 d7906eff .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/10/03 03:53 linux-5.15.y 3a5928702e71 a4c7fd36 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/09/14 18:33 linux-5.15.y 3a5928702e71 c7e35043 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/09/14 09:19 linux-5.15.y 3a5928702e71 c7e35043 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/09/09 02:52 linux-5.15.y 14e468424d3e 9750182a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/07/23 01:44 linux-5.15.y 7c6d66f0266f 708c10c4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/07/17 06:06 linux-5.15.y f45bea23c39c 215bec2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/07/10 06:54 linux-5.15.y f45bea23c39c bc144f9a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/06/30 19:57 linux-5.15.y 4878aadf2d15 757f06b1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/06/30 04:29 linux-5.15.y 4878aadf2d15 757f06b1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/05/01 07:22 linux-5.15.y b925f60c6ee7 3ba885bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/04/29 10:42 linux-5.15.y b925f60c6ee7 27e33c58 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/04/27 22:10 linux-5.15.y b925f60c6ee7 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/04/27 09:43 linux-5.15.y c52b9710c83d 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/04/26 14:47 linux-5.15.y c52b9710c83d 059e9963 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/04/25 21:02 linux-5.15.y c52b9710c83d 8bdc0f22 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/04/25 08:36 linux-5.15.y c52b9710c83d 8bdc0f22 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/04/22 18:05 linux-5.15.y c52b9710c83d 36c961ad .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/04/21 02:33 linux-5.15.y c52b9710c83d af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/04/20 10:44 linux-5.15.y c52b9710c83d af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/04/20 05:46 linux-5.15.y c52b9710c83d af24b050 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/04/20 04:06 linux-5.15.y c52b9710c83d af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/04/17 19:56 linux-5.15.y c52b9710c83d acc528cb .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/04/17 14:24 linux-5.15.y c52b9710c83d 18f6e127 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/04/17 06:20 linux-5.15.y fa3df276cd36 18f6e127 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/04/16 19:02 linux-5.15.y fa3df276cd36 18f6e127 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/04/16 17:37 linux-5.15.y fa3df276cd36 18f6e127 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/04/01 13:22 linux-5.15.y 9465fef4ae35 6baf5069 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/03/29 14:44 linux-5.15.y 9465fef4ae35 c52bcb23 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/03/02 21:01 linux-5.15.y 80efc6265290 25905f5d .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/01/12 11:36 linux-5.15.y 26c690eff0a5 dda5a988 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2023/12/30 09:56 linux-5.15.y d93fa2c78854 fb427a07 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2023/11/14 20:13 linux-5.15.y 80529b4968a8 cb976f63 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2023/08/08 02:24 linux-5.15.y 38d4ca22a528 b1b6ae3d .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2023/07/12 08:47 linux-5.15.y d54cfc420586 2f19aa4f .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2023/06/21 15:15 linux-5.15.y 471e639e59d1 79782afc .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2023/06/16 12:37 linux-5.15.y 471e639e59d1 f3921d4d .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2023/05/22 00:53 linux-5.15.y 9d6bde853685 4bce1a3e .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2023/05/21 19:20 linux-5.15.y 9d6bde853685 4bce1a3e .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2023/05/15 01:15 linux-5.15.y b0ece631f84a 2b9ba477 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2023/03/30 06:48 linux-5.15.y 115472395b0a f325deb0 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in rfcomm_sk_state_change
2024/09/27 21:52 linux-5.15.y 3a5928702e71 440b26ec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/09/26 07:05 linux-5.15.y 3a5928702e71 0d19f247 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/09/24 04:46 linux-5.15.y 3a5928702e71 89298aad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/09/02 08:26 linux-5.15.y fa93fa65db6e 1eda0d14 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/08/30 20:57 linux-5.15.y fa93fa65db6e 1eda0d14 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/08/30 03:10 linux-5.15.y fa93fa65db6e 9bd464fc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/08/28 07:33 linux-5.15.y fa93fa65db6e 6c853ff9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/08/23 01:36 linux-5.15.y fa93fa65db6e ce8a9099 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/08/08 20:47 linux-5.15.y 7e89efd3ae1c 61405512 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/08/08 07:09 linux-5.15.y 7e89efd3ae1c de12cf65 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/08/04 17:50 linux-5.15.y 7e89efd3ae1c 1786a2a8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/07/22 09:14 linux-5.15.y 7c6d66f0266f df655b64 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/05/02 19:21 linux-5.15.y 284087d4f7d5 3ba885bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/05/02 11:57 linux-5.15.y b925f60c6ee7 3ba885bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/05/01 10:18 linux-5.15.y b925f60c6ee7 3ba885bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/05/01 03:55 linux-5.15.y b925f60c6ee7 3ba885bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/30 03:20 linux-5.15.y b925f60c6ee7 f10afd69 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/25 15:53 linux-5.15.y c52b9710c83d 8bdc0f22 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/21 15:46 linux-5.15.y c52b9710c83d af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/21 06:55 linux-5.15.y c52b9710c83d af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/21 00:18 linux-5.15.y c52b9710c83d af24b050 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/19 22:26 linux-5.15.y c52b9710c83d af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/06 13:02 linux-5.15.y 9465fef4ae35 ca620dd8 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/03/31 06:55 linux-5.15.y 9465fef4ae35 6baf5069 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/03/30 10:30 linux-5.15.y 9465fef4ae35 6baf5069 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/03/25 08:05 linux-5.15.y b95c01af2113 0ea90952 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/03/18 17:29 linux-5.15.y b95c01af2113 baa80228 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/03/16 09:32 linux-5.15.y b95c01af2113 d615901c .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/03/01 11:47 linux-5.15.y 458ce51d0356 352ab904 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/02/28 19:39 linux-5.15.y 458ce51d0356 55d6f11d .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/01/18 06:40 linux-5.15.y ddcaf4999061 915053c7 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/12/19 22:42 linux-5.15.y d0fc081c6241 3ad490ea .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/11/04 03:20 linux-5.15.y 12952a23a5da 500bfdc4 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/10/17 07:49 linux-5.15.y 02e21884dcf2 342b9c55 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/09/10 20:30 linux-5.15.y aff03380bda4 6654cf89 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/09/04 22:16 linux-5.15.y 8f790700c974 db3306a6 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/08/27 17:15 linux-5.15.y 5ddfe5cc8716 7ba13a15 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/08/18 08:58 linux-5.15.y f6f7927ac664 74b106b6 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/07/10 22:31 linux-5.15.y d54cfc420586 d47e94ee .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/07/08 01:26 linux-5.15.y d54cfc420586 668cb1fa .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/06/21 11:57 linux-5.15.y 471e639e59d1 79782afc .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/06/16 23:19 linux-5.15.y 471e639e59d1 f3921d4d .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/06/10 06:23 linux-5.15.y 7349e40704a0 9018a337 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/05/26 01:05 linux-5.15.y 1fe619a7d252 0513b3e6 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/03/30 07:34 linux-5.15.y 115472395b0a f325deb0 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/03/24 07:00 linux-5.15.y 115472395b0a f94b4a29 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/03/24 00:34 linux-5.15.y 115472395b0a f94b4a29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in rfcomm_sk_state_change
* Struck through repros no longer work on HEAD.