syzbot


possible deadlock in rfcomm_sk_state_change

Status: upstream: reported C repro on 2023/03/24 09:07
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+71bfc8e67462df154ec3@syzkaller.appspotmail.com
First crash: 452d, last: 47d
Bug presence (2)
Date Name Commit Repro Result
2023/09/15 linux-6.1.y (ToT) 09045dae0d90 C [report] possible deadlock in rfcomm_sk_state_change
2023/09/15 upstream (ToT) 9fdfb15a3dbf C Didn't crash
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 possible deadlock in rfcomm_sk_state_change origin:upstream C error 423 47d 453d 0/3 upstream: reported C repro on 2023/03/24 00:34
upstream possible deadlock in rfcomm_sk_state_change bluetooth C done 21745 5d04h 1010d 0/27 upstream: reported C repro on 2021/09/13 05:15
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2023/09/22 23:04 6h26m fix candidate upstream job log (1)

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

but task is already holding lock:
ffff8880285e8d28 (&d->lock){+.+.}-{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:

-> #3 (&d->lock){+.+.}-{3:3}:
       lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x132/0xd80 kernel/locking/mutex.c:747
       __rfcomm_dlc_close+0x259/0x6d0 net/bluetooth/rfcomm/core.c:487
       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
       rfcomm_sock_release+0x55/0x110 net/bluetooth/rfcomm/sock.c:933
       __sock_release net/socket.c:654 [inline]
       sock_close+0xcd/0x230 net/socket.c:1400
       __fput+0x3b7/0x890 fs/file_table.c:320
       task_work_run+0x246/0x300 kernel/task_work.c:179
       exit_task_work include/linux/task_work.h:38 [inline]
       do_exit+0xa73/0x26a0 kernel/exit.c:869
       do_group_exit+0x202/0x2b0 kernel/exit.c:1019
       get_signal+0x16f7/0x17d0 kernel/signal.c:2862
       arch_do_signal_or_restart+0xb0/0x1a10 arch/x86/kernel/signal.c:871
       exit_to_user_mode_loop+0x6a/0x100 kernel/entry/common.c:174
       exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
       __syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline]
       syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:303
       do_syscall_64+0x47/0xb0 arch/x86/entry/common.c:87
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #2 (rfcomm_mutex){+.+.}-{3:3}:
       lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x132/0xd80 kernel/locking/mutex.c:747
       rfcomm_dlc_exists+0xa2/0x370 net/bluetooth/rfcomm/core.c:542
       __rfcomm_create_dev net/bluetooth/rfcomm/tty.c:414 [inline]
       rfcomm_create_dev net/bluetooth/rfcomm/tty.c:485 [inline]
       rfcomm_dev_ioctl+0xb2d/0x2180 net/bluetooth/rfcomm/tty.c:587
       rfcomm_sock_ioctl+0x82/0xc0 net/bluetooth/rfcomm/sock.c:880
       sock_do_ioctl+0x152/0x450 net/socket.c:1204
       sock_ioctl+0x47f/0x770 net/socket.c:1321
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:870 [inline]
       __se_sys_ioctl+0xf1/0x160 fs/ioctl.c:856
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #1 (rfcomm_ioctl_mutex){+.+.}-{3:3}:
       lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x132/0xd80 kernel/locking/mutex.c:747
       rfcomm_create_dev net/bluetooth/rfcomm/tty.c:484 [inline]
       rfcomm_dev_ioctl+0x233/0x2180 net/bluetooth/rfcomm/tty.c:587
       rfcomm_sock_ioctl+0x82/0xc0 net/bluetooth/rfcomm/sock.c:880
       sock_do_ioctl+0x152/0x450 net/socket.c:1204
       sock_ioctl+0x47f/0x770 net/socket.c:1321
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:870 [inline]
       __se_sys_ioctl+0xf1/0x160 fs/ioctl.c:856
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #0 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}:
       check_prev_add kernel/locking/lockdep.c:3090 [inline]
       check_prevs_add kernel/locking/lockdep.c:3209 [inline]
       validate_chain+0x1661/0x5950 kernel/locking/lockdep.c:3825
       __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5049
       lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662
       lock_sock_nested+0x44/0x100 net/core/sock.c:3484
       lock_sock include/net/sock.h:1745 [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
       rfcomm_sock_release+0x55/0x110 net/bluetooth/rfcomm/sock.c:933
       __sock_release net/socket.c:654 [inline]
       sock_close+0xcd/0x230 net/socket.c:1400
       __fput+0x3b7/0x890 fs/file_table.c:320
       task_work_run+0x246/0x300 kernel/task_work.c:179
       exit_task_work include/linux/task_work.h:38 [inline]
       do_exit+0xa73/0x26a0 kernel/exit.c:869
       do_group_exit+0x202/0x2b0 kernel/exit.c:1019
       get_signal+0x16f7/0x17d0 kernel/signal.c:2862
       arch_do_signal_or_restart+0xb0/0x1a10 arch/x86/kernel/signal.c:871
       exit_to_user_mode_loop+0x6a/0x100 kernel/entry/common.c:174
       exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
       __syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline]
       syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:303
       do_syscall_64+0x47/0xb0 arch/x86/entry/common.c:87
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

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-executor423/3572:
 #0: ffff88806f403e10 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
 #0: ffff88806f403e10 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: __sock_release net/socket.c:653 [inline]
 #0: ffff88806f403e10 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: sock_close+0x98/0x230 net/socket.c:1400
 #1: ffffffff8e414e88 (rfcomm_mutex){+.+.}-{3:3}, at: rfcomm_dlc_close+0x37/0x180 net/bluetooth/rfcomm/core.c:507
 #2: ffff8880285e8d28 (&d->lock){+.+.}-{3:3}, at: __rfcomm_dlc_close+0x259/0x6d0 net/bluetooth/rfcomm/core.c:487

stack backtrace:
CPU: 1 PID: 3572 Comm: syz-executor423 Not tainted 6.1.87-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
 check_noncircular+0x2fa/0x3b0 kernel/locking/lockdep.c:2170
 check_prev_add kernel/locking/lockdep.c:3090 [inline]
 check_prevs_add kernel/locking/lockdep.c:3209 [inline]
 validate_chain+0x1661/0x5950 kernel/locking/lockdep.c:3825
 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5049
 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662
 lock_sock_nested+0x44/0x100 net/core/sock.c:3484
 lock_sock include/net/sock.h:1745 [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
 rfcomm_sock_release+0x55/0x110 net/bluetooth/rfcomm/sock.c:933
 __sock_release net/socket.c:654 [inline]
 sock_close+0xcd/0x230 net/socket.c:1400
 __fput+0x3b7/0x890 fs/file_table.c:320
 task_work_run+0x246/0x300 kernel/task_work.c:179
 exit_task_work include/linux/task_work.h:38 [inline]
 do_exit+0xa73/0x26a0 kernel/exit.c:869
 do_group_exit+0x202/0x2b0 kernel/exit.c:1019
 get_signal+0x16f7/0x17d0 kernel/signal.c:2862
 arch_do_signal_or_restart+0xb0/0x1a10 arch/x86/kernel/signal.c:871
 exit_to_user_mode_loop+0x6a/0x100 kernel/entry/common.c:174
 exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
 __syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline]
 syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:303
 do_syscall_64+0x47/0xb0 arch/x86/entry/common.c:87
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7ff8ba758fb9
Code: Unable to access opcode bytes at 0x7ff8ba758f8f.
RSP: 002b:00007fff901e1808 EFLAGS: 00000246 ORIG_RAX: 000000000000002a
RAX: fffffffffffffffc RBX: 0000000000000000 RCX: 00007ff8ba758fb9
RDX: 000000000000000a RSI: 0000000020000200 RDI: 0000000000000004
RBP: 00000000000f4240 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000004 R14: 00007fff901e1880 R15: 00007fff901e1870
 </TASK>

Crashes (296):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/21 23:23 linux-6.1.y 6741e066ec76 af24b050 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/08 21:00 linux-6.1.y 347385861c50 53df08b6 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/03/29 00:46 linux-6.1.y e5cd595e23c1 e91187ee .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/03/01 05:24 linux-6.1.y 81e1dc2f7001 352ab904 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/01/03 18:51 linux-6.1.y a507f147e6f0 fb427a07 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2023/12/28 07:52 linux-6.1.y 4aa6747d9352 fb427a07 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2023/10/31 20:22 linux-6.1.y 32c9cdbe383c 58499c95 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2023/09/20 07:09 linux-6.1.y a356197db198 0b6a67ac .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2023/09/14 10:57 linux-6.1.y 09045dae0d90 0b6a67ac .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/21 02:01 linux-6.1.y 6741e066ec76 af24b050 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/17 06:40 linux-6.1.y cd5d98c0556c 18f6e127 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/16 14:28 linux-6.1.y cd5d98c0556c 0d592ce4 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/15 18:37 linux-6.1.y cd5d98c0556c b9af7e61 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/03/29 03:02 linux-6.1.y e5cd595e23c1 e91187ee .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/03/23 03:35 linux-6.1.y d7543167affd 4b6cdce6 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/03/23 03:05 linux-6.1.y d7543167affd 4b6cdce6 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/03/17 07:12 linux-6.1.y d7543167affd d615901c .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/03/15 10:30 linux-6.1.y 61adba85cc40 d615901c .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/03/07 03:12 linux-6.1.y 61adba85cc40 f39a7eed .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/02/26 20:02 linux-6.1.y 81e1dc2f7001 da36a36b .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/01/29 21:03 linux-6.1.y 883d1a956208 991a98f4 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/01/20 17:37 linux-6.1.y 8fd7f4462453 9bd8dcda .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/01/16 08:56 linux-6.1.y fec3b1451d5f 2a7bcc7f .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/01/05 12:07 linux-6.1.y a507f147e6f0 28c42cff .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/12/27 06:56 linux-6.1.y 4aa6747d9352 fb427a07 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/12/25 15:04 linux-6.1.y 4aa6747d9352 fb427a07 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/11/24 04:51 linux-6.1.y 69e434a1cb21 5b429f39 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/11/14 21:21 linux-6.1.y fb2635ac69ab cb976f63 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/11/14 19:28 linux-6.1.y fb2635ac69ab cb976f63 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/03/30 07:33 linux-6.1.y e3a87a10f259 f325deb0 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/08/16 11:05 linux-6.1.y 1321ab403b38 39990d51 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2023/06/27 18:20 linux-6.1.y e84a4e368abe 4cd5bb25 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2023/05/24 05:05 linux-6.1.y fa74641fb6b9 4bce1a3e .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2023/05/23 23:17 linux-6.1.y fa74641fb6b9 4bce1a3e .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2023/05/22 03:23 linux-6.1.y fa74641fb6b9 4bce1a3e .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2023/08/12 19:40 linux-6.1.y 1321ab403b38 39990d51 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/07/19 04:02 linux-6.1.y 61fd484b2cf6 022df2bb .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/06/20 00:08 linux-6.1.y ca87e77a2ef8 d521bc56 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/06/16 23:29 linux-6.1.y ca87e77a2ef8 f3921d4d .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/06/10 09:16 linux-6.1.y 2f3918bc53fb 9018a337 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/05/27 09:41 linux-6.1.y a343b0dd87b4 cf184559 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2023/03/24 09:07 linux-6.1.y e3a87a10f259 f94b4a29 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/30 13:20 linux-6.1.y dcbc050cb0d3 3ce4924c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/30 11:29 linux-6.1.y dcbc050cb0d3 3ce4924c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/30 01:49 linux-6.1.y dcbc050cb0d3 f10afd69 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/23 14:38 linux-6.1.y 6741e066ec76 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/23 12:19 linux-6.1.y 6741e066ec76 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/22 04:06 linux-6.1.y 6741e066ec76 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/21 12:07 linux-6.1.y 6741e066ec76 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/19 14:51 linux-6.1.y 6741e066ec76 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/18 14:08 linux-6.1.y 6741e066ec76 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/18 11:21 linux-6.1.y 6741e066ec76 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/17 22:25 linux-6.1.y 6741e066ec76 acc528cb .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/16 18:20 linux-6.1.y cd5d98c0556c 18f6e127 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/15 16:10 linux-6.1.y cd5d98c0556c b9af7e61 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/14 07:33 linux-6.1.y cd5d98c0556c c8349e48 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/13 07:21 linux-6.1.y bf1e3b1cb1e0 c8349e48 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/11 04:13 linux-6.1.y bf1e3b1cb1e0 33b9e058 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/10 17:16 linux-6.1.y bf1e3b1cb1e0 4320ec32 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/10 04:15 linux-6.1.y 347385861c50 171ec371 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/09 22:16 linux-6.1.y 347385861c50 171ec371 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/09 15:31 linux-6.1.y 347385861c50 f3234354 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/08 17:09 linux-6.1.y 347385861c50 53df08b6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/08 15:09 linux-6.1.y 347385861c50 53df08b6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/07 18:49 linux-6.1.y 347385861c50 ca620dd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/07 03:44 linux-6.1.y 347385861c50 ca620dd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/04/07 00:49 linux-6.1.y 347385861c50 ca620dd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan possible deadlock in rfcomm_sk_state_change
2024/05/02 06:32 linux-6.1.y dcbc050cb0d3 3ba885bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/05/01 07:26 linux-6.1.y dcbc050cb0d3 3ba885bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/05/01 05:51 linux-6.1.y dcbc050cb0d3 3ba885bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/05/01 01:15 linux-6.1.y dcbc050cb0d3 3ba885bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/27 21:06 linux-6.1.y f2295faba5e8 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/27 17:07 linux-6.1.y f2295faba5e8 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/27 06:16 linux-6.1.y 6741e066ec76 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/26 12:54 linux-6.1.y 6741e066ec76 059e9963 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/23 09:22 linux-6.1.y 6741e066ec76 21339d7b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/22 02:24 linux-6.1.y 6741e066ec76 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/20 22:54 linux-6.1.y 6741e066ec76 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/19 16:27 linux-6.1.y 6741e066ec76 af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/17 18:00 linux-6.1.y 6741e066ec76 acc528cb .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/16 10:55 linux-6.1.y cd5d98c0556c 0d592ce4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/16 06:10 linux-6.1.y cd5d98c0556c 0d592ce4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/13 21:44 linux-6.1.y cd5d98c0556c c8349e48 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/11 14:23 linux-6.1.y bf1e3b1cb1e0 95ed9ece .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/09 05:20 linux-6.1.y 347385861c50 f3234354 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/08 06:47 linux-6.1.y 347385861c50 ca620dd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/07 20:41 linux-6.1.y 347385861c50 ca620dd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
2024/04/06 06:34 linux-6.1.y 347385861c50 ca620dd8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 possible deadlock in rfcomm_sk_state_change
* Struck through repros no longer work on HEAD.