syzbot


possible deadlock in __loop_clr_fd

Status: upstream: reported C repro on 2023/03/09 14:25
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+a94f42fb4f5d3739ef4a@syzkaller.appspotmail.com
First crash: 1231d, last: 1h46m
Fix commit to backport (bisect log) :
tree: upstream
commit fbdee71bb5d8d054e1bdb5af4c540f2cb86fe296
Author: Christoph Hellwig <hch@lst.de>
Date: Tue Jan 4 07:16:47 2022 +0000

  block: deprecate autoloading based on dev_t

[report pending]
  
Bug presence (2)
Date Name Commit Repro Result
2023/08/31 linux-5.15.y (ToT) 9e43368a3393 C [report] possible deadlock in __loop_clr_fd
2023/08/31 upstream (ToT) 87dfd85c3892 C Didn't crash
Similar bugs (3)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in __loop_clr_fd (2) block ext4 4 C unreliable 6977 1716d 1841d 20/29 fixed on 2021/11/10 00:50
upstream possible deadlock in __loop_clr_fd block 4 2 1951d 1947d 0/29 auto-closed as invalid on 2021/05/18 10:52
upstream possible deadlock in __loop_clr_fd (3) block 4 2972 1652d 1715d 20/29 fixed on 2022/03/08 16:11
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2023/10/09 19:15 4h39m fix candidate upstream OK (1) job log

Sample crash report:
 loop7: unable to read partition table
loop7: partition table beyond EOD, truncated
loop_reread_partitions: partition scan of loop7 (Cj̖P=ý?}X	%`ր{֐ȵ4FLQk݊) failed (rc=-5)
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.17/4346 is trying to acquire lock:
ffff888072410938 ((wq_completion)loop7){+.+.}-{0:0}, at: flush_workqueue+0x14e/0x1390 kernel/workqueue.c:2830

but task is already holding lock:
ffff8881471b5468 (&lo->lo_mutex){+.+.}-{3:3}, at: __loop_clr_fd+0xa9/0xb50 drivers/block/loop.c:1366

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #6 (&lo->lo_mutex){+.+.}-{3:3}:
       __mutex_lock_common+0x1e5/0x2400 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_killable_nested+0x17/0x20 kernel/locking/mutex.c:758
       lo_open+0x6a/0x100 drivers/block/loop.c:2056
       blkdev_get_whole+0x90/0x390 block/bdev.c:669
       blkdev_get_by_dev+0x2da/0xa50 block/bdev.c:827
       blkdev_open+0x128/0x2c0 block/fops.c:466
       do_dentry_open+0x7f7/0xf90 fs/open.c:826
       do_open fs/namei.c:3616 [inline]
       path_openat+0x2718/0x2fb0 fs/namei.c:3750
       do_filp_open+0x1df/0x400 fs/namei.c:3777
       do_sys_openat2+0x14b/0x500 fs/open.c:1255
       do_sys_open fs/open.c:1271 [inline]
       __do_sys_openat fs/open.c:1287 [inline]
       __se_sys_openat fs/open.c:1282 [inline]
       __x64_sys_openat+0x135/0x160 fs/open.c:1282
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #5 (&disk->open_mutex){+.+.}-{3:3}:
       __mutex_lock_common+0x1e5/0x2400 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
       blkdev_get_by_dev+0x162/0xa50 block/bdev.c:820
       swsusp_check+0xa1/0x2b0 kernel/power/swap.c:1526
       software_resume+0xc6/0x3b0 kernel/power/hibernate.c:982
       resume_store+0xe4/0x130 kernel/power/hibernate.c:1184
       kernfs_fop_write_iter+0x3a8/0x500 fs/kernfs/file.c:296
       call_write_iter include/linux/fs.h:2173 [inline]
       new_sync_write fs/read_write.c:507 [inline]
       vfs_write+0x748/0xd70 fs/read_write.c:594
       ksys_write+0x153/0x260 fs/read_write.c:647
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #4 (system_transition_mutex/1){+.+.}-{3:3}:
       __mutex_lock_common+0x1e5/0x2400 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
       software_resume+0x7c/0x3b0 kernel/power/hibernate.c:937
       resume_store+0xe4/0x130 kernel/power/hibernate.c:1184
       kernfs_fop_write_iter+0x3a8/0x500 fs/kernfs/file.c:296
       call_write_iter include/linux/fs.h:2173 [inline]
       new_sync_write fs/read_write.c:507 [inline]
       vfs_write+0x748/0xd70 fs/read_write.c:594
       ksys_write+0x153/0x260 fs/read_write.c:647
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #3 (&of->mutex){+.+.}-{3:3}:
       __mutex_lock_common+0x1e5/0x2400 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
       kernfs_seq_start+0x55/0x3c0 fs/kernfs/file.c:112
       seq_read_iter+0x387/0xc50 fs/seq_file.c:225
       call_read_iter include/linux/fs.h:2167 [inline]
       new_sync_read fs/read_write.c:404 [inline]
       vfs_read+0x75e/0xd50 fs/read_write.c:485
       ksys_read+0x153/0x260 fs/read_write.c:623
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #2 (&p->lock){+.+.}-{3:3}:
       __mutex_lock_common+0x1e5/0x2400 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
       seq_read_iter+0x9d/0xc50 fs/seq_file.c:182
       do_iter_readv_writev+0x47d/0x5f0 fs/read_write.c:-1
       do_iter_read+0x201/0x7c0 fs/read_write.c:790
       lo_read_simple drivers/block/loop.c:392 [inline]
       do_req_filebacked drivers/block/loop.c:663 [inline]
       loop_handle_cmd drivers/block/loop.c:2235 [inline]
       loop_process_work+0x16fd/0x24c0 drivers/block/loop.c:2275
       process_one_work+0x867/0xff0 kernel/workqueue.c:2310
       worker_thread+0xad7/0x12a0 kernel/workqueue.c:2457
       kthread+0x42e/0x520 kernel/kthread.c:334
       ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287

-> #1 ((work_completion)(&worker->work)){+.+.}-{0:0}:
       process_one_work+0x7ba/0xff0 kernel/workqueue.c:2286
       worker_thread+0xad7/0x12a0 kernel/workqueue.c:2457
       kthread+0x42e/0x520 kernel/kthread.c:334
       ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287

-> #0 ((wq_completion)loop7){+.+.}-{0:0}:
       check_prev_add kernel/locking/lockdep.c:3053 [inline]
       check_prevs_add kernel/locking/lockdep.c:3172 [inline]
       validate_chain kernel/locking/lockdep.c:3788 [inline]
       __lock_acquire+0x2c66/0x7b50 kernel/locking/lockdep.c:5012
       lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
       flush_workqueue+0x16a/0x1390 kernel/workqueue.c:2830
       drain_workqueue+0xca/0x370 kernel/workqueue.c:2995
       destroy_workqueue+0x7b/0xb20 kernel/workqueue.c:4439
       __loop_clr_fd+0x22f/0xb50 drivers/block/loop.c:1384
       blkdev_put+0x52b/0x780 block/bdev.c:-1
       blkdev_close+0x76/0xa0 block/fops.c:478
       __fput+0x212/0x8c0 fs/file_table.c:311
       task_work_run+0x125/0x1a0 kernel/task_work.c:188
       tracehook_notify_resume include/linux/tracehook.h:189 [inline]
       exit_to_user_mode_loop+0x10f/0x130 kernel/entry/common.c:181
       exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:214
       __syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline]
       syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:307
       do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:86
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

other info that might help us debug this:

Chain exists of:
  (wq_completion)loop7 --> &disk->open_mutex --> &lo->lo_mutex

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&lo->lo_mutex);
                               lock(&disk->open_mutex);
                               lock(&lo->lo_mutex);
  lock((wq_completion)loop7);

 *** DEADLOCK ***

2 locks held by syz.0.17/4346:
 #0: ffff888020a88518 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xf1/0x780 block/bdev.c:915
 #1: ffff8881471b5468 (&lo->lo_mutex){+.+.}-{3:3}, at: __loop_clr_fd+0xa9/0xb50 drivers/block/loop.c:1366

stack backtrace:
CPU: 1 PID: 4346 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/25/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
 check_noncircular+0x296/0x330 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 kernel/locking/lockdep.c:3788 [inline]
 __lock_acquire+0x2c66/0x7b50 kernel/locking/lockdep.c:5012
 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
 flush_workqueue+0x16a/0x1390 kernel/workqueue.c:2830
 drain_workqueue+0xca/0x370 kernel/workqueue.c:2995
 destroy_workqueue+0x7b/0xb20 kernel/workqueue.c:4439
 __loop_clr_fd+0x22f/0xb50 drivers/block/loop.c:1384
 blkdev_put+0x52b/0x780 block/bdev.c:-1
 blkdev_close+0x76/0xa0 block/fops.c:478
 __fput+0x212/0x8c0 fs/file_table.c:311
 task_work_run+0x125/0x1a0 kernel/task_work.c:188
 tracehook_notify_resume include/linux/tracehook.h:189 [inline]
 exit_to_user_mode_loop+0x10f/0x130 kernel/entry/common.c:181
 exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:214
 __syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline]
 syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:307
 do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f35146a9e59
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe72566798 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 00007ffe72566880 RCX: 00007f35146a9e59
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 0000000000013246 R08: 0000000000000001 R09: 0000000000000000
R10: 0000001b30120000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f3514931fac R14: 00007f3514931fa8 R15: 00007f3514931fa0
 </TASK>

Crashes (9660):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/07/17 01:12 linux-5.15.y c86c4726e7f0 71b49442 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/04/07 03:51 linux-5.15.y 91d48252ad4b 4440e7c2 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/01/13 06:31 linux-5.15.y 68efe5a6c16a d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/08/06 18:33 linux-5.15.y c79648372d02 ffe1dd46 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/22 12:12 linux-5.15.y c79648372d02 1555463b .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/01 09:22 linux-5.15.y 3dea0e7f549e 6e83b42d .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/06/10 12:23 linux-5.15.y 1c700860e8bc 4826c28e .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/01/18 14:54 linux-5.15.y 4735586da88e f2cb035c .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/01/06 18:44 linux-5.15.y 91786f140358 f3558dbf .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/10/28 05:43 linux-5.15.y 74cdd62cb470 65e8686b .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/10/08 21:23 linux-5.15.y 3a5928702e71 402f1df0 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/08/25 13:27 linux-5.15.y fa93fa65db6e d7d32352 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/05/19 17:38 linux-5.15.y 83655231580b c0f1611a .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2023/08/25 01:43 linux-5.15.y f6f7927ac664 49be837e .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/03/16 10:03 linux-5.15.y b95c01af2113 d615901c .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 possible deadlock in __loop_clr_fd
2024/04/17 02:10 linux-5.15.y fa3df276cd36 18f6e127 .config console log report syz [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/01/08 13:15 linux-5.15.y 26c690eff0a5 d0304e9c .config console log report syz [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/02/28 22:36 linux-5.15.y 458ce51d0356 55d6f11d .config console log report syz [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in __loop_clr_fd
2023/06/05 22:48 linux-5.15.y d7af3e5ba454 a4ae4f42 .config console log report syz [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in __loop_clr_fd
2023/06/26 03:35 linux-5.15.y f67653019430 79782afc .config console log report syz [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2023/08/06 02:27 linux-5.15.y 38d4ca22a528 4ffcc9ef .config console log report syz [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in __loop_clr_fd
2023/07/10 21:34 linux-5.15.y d54cfc420586 d47e94ee .config console log report syz [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in __loop_clr_fd
2026/07/23 00:28 linux-5.15.y c86c4726e7f0 881ce5c2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/22 21:11 linux-5.15.y c86c4726e7f0 4a865b71 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/22 19:26 linux-5.15.y c86c4726e7f0 4a865b71 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/22 15:14 linux-5.15.y c86c4726e7f0 4a865b71 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/22 12:31 linux-5.15.y c86c4726e7f0 4a865b71 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/21 23:52 linux-5.15.y c86c4726e7f0 b561ce9c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/21 14:37 linux-5.15.y c86c4726e7f0 7c5de9c3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/21 08:10 linux-5.15.y c86c4726e7f0 de6a700d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/21 05:14 linux-5.15.y c86c4726e7f0 de6a700d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/20 13:40 linux-5.15.y c86c4726e7f0 de6a700d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/20 07:18 linux-5.15.y c86c4726e7f0 72524a66 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/20 00:24 linux-5.15.y c86c4726e7f0 72524a66 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/19 22:50 linux-5.15.y c86c4726e7f0 72524a66 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/19 20:53 linux-5.15.y c86c4726e7f0 72524a66 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/19 03:48 linux-5.15.y c86c4726e7f0 72524a66 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/18 08:35 linux-5.15.y c86c4726e7f0 72524a66 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/17 20:25 linux-5.15.y c86c4726e7f0 8aaff637 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/17 18:19 linux-5.15.y c86c4726e7f0 8aaff637 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/17 09:07 linux-5.15.y c86c4726e7f0 7f27c57a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/17 07:43 linux-5.15.y c86c4726e7f0 7f27c57a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/17 07:42 linux-5.15.y c86c4726e7f0 7f27c57a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/17 04:40 linux-5.15.y c86c4726e7f0 7f27c57a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/16 17:54 linux-5.15.y c86c4726e7f0 71b49442 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/15 23:50 linux-5.15.y c86c4726e7f0 27a8bd60 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/15 16:08 linux-5.15.y c86c4726e7f0 a4ed0f4f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/15 09:48 linux-5.15.y c86c4726e7f0 a4ed0f4f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/15 06:38 linux-5.15.y c86c4726e7f0 2130f682 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/14 01:37 linux-5.15.y c86c4726e7f0 2130f682 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/13 19:43 linux-5.15.y c86c4726e7f0 cc4833d0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/13 17:56 linux-5.15.y c86c4726e7f0 cc4833d0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/13 13:03 linux-5.15.y c86c4726e7f0 cc4833d0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/13 10:30 linux-5.15.y c86c4726e7f0 d78ea535 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/13 09:02 linux-5.15.y c86c4726e7f0 d78ea535 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/12 21:52 linux-5.15.y c86c4726e7f0 d78ea535 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/12 19:50 linux-5.15.y c86c4726e7f0 d78ea535 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/10 18:04 linux-5.15.y c86c4726e7f0 99e64375 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/09 14:18 linux-5.15.y c86c4726e7f0 a0c310a3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/09 09:47 linux-5.15.y c86c4726e7f0 b9f1ceaa .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/09 04:06 linux-5.15.y c86c4726e7f0 b9f1ceaa .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/08 08:05 linux-5.15.y c86c4726e7f0 76cdc0c0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/08 01:52 linux-5.15.y c86c4726e7f0 76cdc0c0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/07 22:01 linux-5.15.y c86c4726e7f0 76cdc0c0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/07 22:01 linux-5.15.y c86c4726e7f0 76cdc0c0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2026/07/07 05:56 linux-5.15.y c86c4726e7f0 8e71ce95 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/08/28 06:09 linux-5.15.y c79648372d02 e12e5ba4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in __loop_clr_fd
2023/03/09 14:24 linux-5.15.y d9b4a0c83a2d f08b59ac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
* Struck through repros no longer work on HEAD.