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: 851d, last: 7h20m
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 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in __loop_clr_fd (2) block ext4 C unreliable 6977 1336d 1461d 20/29 fixed on 2021/11/10 00:50
upstream possible deadlock in __loop_clr_fd block 2 1571d 1568d 0/29 auto-closed as invalid on 2021/05/18 10:52
upstream possible deadlock in __loop_clr_fd (3) block 2972 1272d 1335d 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:
XFS (loop0): Unmounting Filesystem
======================================================
WARNING: possible circular locking dependency detected
5.15.186-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor/4269 is trying to acquire lock:
ffff88807e3a1938 ((wq_completion)loop0){+.+.}-{0:0}, at: flush_workqueue+0x126/0x1380 kernel/workqueue.c:2830

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

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #7 (&lo->lo_mutex){+.+.}-{3:3}:
       __mutex_lock_common+0x1eb/0x2390 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+0x2d0/0xa60 block/bdev.c:827
       blkdev_open+0x12d/0x2c0 block/fops.c:466
       do_dentry_open+0x7ff/0xf80 fs/open.c:826
       do_open fs/namei.c:3608 [inline]
       path_openat+0x2682/0x2f30 fs/namei.c:3742
       do_filp_open+0x1b3/0x3e0 fs/namei.c:3769
       do_sys_openat2+0x142/0x4a0 fs/open.c:1253
       do_sys_open fs/open.c:1269 [inline]
       __do_sys_openat fs/open.c:1285 [inline]
       __se_sys_openat fs/open.c:1280 [inline]
       __x64_sys_openat+0x135/0x160 fs/open.c:1280
       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

-> #6 (&disk->open_mutex){+.+.}-{3:3}:
       __mutex_lock_common+0x1eb/0x2390 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+0x157/0xa60 block/bdev.c:820
       swsusp_check+0x9b/0x2a0 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+0x379/0x4c0 fs/kernfs/file.c:296
       call_write_iter include/linux/fs.h:2172 [inline]
       new_sync_write fs/read_write.c:507 [inline]
       vfs_write+0x712/0xd00 fs/read_write.c:594
       ksys_write+0x14d/0x250 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

-> #5 (system_transition_mutex/1){+.+.}-{3:3}:
       __mutex_lock_common+0x1eb/0x2390 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+0x379/0x4c0 fs/kernfs/file.c:296
       call_write_iter include/linux/fs.h:2172 [inline]
       new_sync_write fs/read_write.c:507 [inline]
       vfs_write+0x712/0xd00 fs/read_write.c:594
       ksys_write+0x14d/0x250 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 (&of->mutex){+.+.}-{3:3}:
       __mutex_lock_common+0x1eb/0x2390 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+0x51/0x3c0 fs/kernfs/file.c:112
       seq_read_iter+0x3c4/0xd50 fs/seq_file.c:225
       call_read_iter include/linux/fs.h:2166 [inline]
       new_sync_read fs/read_write.c:404 [inline]
       vfs_read+0x725/0xcf0 fs/read_write.c:485
       ksys_read+0x14d/0x250 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

-> #3 (&p->lock){+.+.}-{3:3}:
       __mutex_lock_common+0x1eb/0x2390 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+0xad/0xd50 fs/seq_file.c:182
       call_read_iter include/linux/fs.h:2166 [inline]
       generic_file_splice_read+0x3a2/0x590 fs/splice.c:311
       do_splice_to fs/splice.c:796 [inline]
       splice_direct_to_actor+0x413/0xb50 fs/splice.c:870
       do_splice_direct+0x1b9/0x2c0 fs/splice.c:979
       do_sendfile+0x5d5/0xec0 fs/read_write.c:1249
       __do_sys_sendfile64 fs/read_write.c:1317 [inline]
       __se_sys_sendfile64+0x13b/0x190 fs/read_write.c:1303
       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 (sb_writers#3){.+.+}-{0:0}:
       percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
       __sb_start_write include/linux/fs.h:1811 [inline]
       sb_start_write include/linux/fs.h:1881 [inline]
       file_start_write include/linux/fs.h:3042 [inline]
       lo_write_bvec+0x193/0x770 drivers/block/loop.c:315
       lo_write_simple drivers/block/loop.c:338 [inline]
       do_req_filebacked drivers/block/loop.c:656 [inline]
       loop_handle_cmd drivers/block/loop.c:2235 [inline]
       loop_process_work+0x1d62/0x2480 drivers/block/loop.c:2275
       process_one_work+0x863/0x1000 kernel/workqueue.c:2310
       worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457
       kthread+0x436/0x520 kernel/kthread.c:334
       ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287

-> #1 ((work_completion)(&lo->rootcg_work)){+.+.}-{0:0}:
       process_one_work+0x7bf/0x1000 kernel/workqueue.c:2286
       worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457
       kthread+0x436/0x520 kernel/kthread.c:334
       ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287

-> #0 ((wq_completion)loop0){+.+.}-{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+0x2c33/0x7c60 kernel/locking/lockdep.c:5012
       lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
       flush_workqueue+0x142/0x1380 kernel/workqueue.c:2830
       drain_workqueue+0xcf/0x380 kernel/workqueue.c:2995
       destroy_workqueue+0x7b/0xb20 kernel/workqueue.c:4439
       __loop_clr_fd+0x234/0xb90 drivers/block/loop.c:1384
       blkdev_put_whole block/bdev.c:692 [inline]
       blkdev_put+0x53f/0x7d0 block/bdev.c:957
       deactivate_locked_super+0x93/0xf0 fs/super.c:335
       cleanup_mnt+0x418/0x4d0 fs/namespace.c:1139
       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+0xb1/0x140 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)loop0 --> &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)loop0);

 *** DEADLOCK ***

2 locks held by syz-executor/4269:
 #0: ffff88801ff60518 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xf9/0x7d0 block/bdev.c:915
 #1: ffff8881474f9468 (&lo->lo_mutex){+.+.}-{3:3}, at: __loop_clr_fd+0xaa/0xb90 drivers/block/loop.c:1366

stack backtrace:
CPU: 1 PID: 4269 Comm: syz-executor Not tainted 5.15.186-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
 check_noncircular+0x274/0x310 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+0x2c33/0x7c60 kernel/locking/lockdep.c:5012
 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
 flush_workqueue+0x142/0x1380 kernel/workqueue.c:2830
 drain_workqueue+0xcf/0x380 kernel/workqueue.c:2995
 destroy_workqueue+0x7b/0xb20 kernel/workqueue.c:4439
 __loop_clr_fd+0x234/0xb90 drivers/block/loop.c:1384
 blkdev_put_whole block/bdev.c:692 [inline]
 blkdev_put+0x53f/0x7d0 block/bdev.c:957
 deactivate_locked_super+0x93/0xf0 fs/super.c:335
 cleanup_mnt+0x418/0x4d0 fs/namespace.c:1139
 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+0xb1/0x140 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:0x7feaf4b9dc57
Code: a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 a8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffcb90034b8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007feaf4c1e925 RCX: 00007feaf4b9dc57
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffcb9003570
RBP: 00007ffcb9003570 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffcb9004600
R13: 00007feaf4c1e925 R14: 000000000000fbac R15: 00007ffcb9004640
 </TASK>

Crashes (6215):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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
2025/07/08 00:19 linux-5.15.y 3dea0e7f549e 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/07 22:00 linux-5.15.y 3dea0e7f549e 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/07 16:01 linux-5.15.y 3dea0e7f549e 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/07 05:38 linux-5.15.y 3dea0e7f549e 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/07 00:13 linux-5.15.y 3dea0e7f549e 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/06 18:20 linux-5.15.y 3dea0e7f549e 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/06 07:29 linux-5.15.y 3dea0e7f549e 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/06 04:30 linux-5.15.y 3dea0e7f549e 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/06 00:41 linux-5.15.y 3dea0e7f549e 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/05 16:46 linux-5.15.y 3dea0e7f549e 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/05 11:02 linux-5.15.y 3dea0e7f549e 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/05 08:15 linux-5.15.y 3dea0e7f549e 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/05 01:41 linux-5.15.y 3dea0e7f549e d869b261 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/05 00:49 linux-5.15.y 3dea0e7f549e d869b261 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/04 09:01 linux-5.15.y 3dea0e7f549e 76ad128c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/04 06:03 linux-5.15.y 3dea0e7f549e 76ad128c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/04 00:56 linux-5.15.y 3dea0e7f549e 76ad128c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/03 21:33 linux-5.15.y 3dea0e7f549e 115ceea7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/03 19:20 linux-5.15.y 3dea0e7f549e 115ceea7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/03 10:47 linux-5.15.y 3dea0e7f549e 115ceea7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/03 05:59 linux-5.15.y 3dea0e7f549e 115ceea7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/02 20:58 linux-5.15.y 3dea0e7f549e bc80e4f0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/02 19:15 linux-5.15.y 3dea0e7f549e bc80e4f0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/02 14:51 linux-5.15.y 3dea0e7f549e bc80e4f0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/02 03:10 linux-5.15.y 3dea0e7f549e 091a06cd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/02 00:34 linux-5.15.y 3dea0e7f549e 091a06cd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/01 16:53 linux-5.15.y 3dea0e7f549e 091a06cd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/01 12:48 linux-5.15.y 3dea0e7f549e 6e83b42d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/01 05:21 linux-5.15.y 3dea0e7f549e 6e83b42d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/06/30 20:45 linux-5.15.y 3dea0e7f549e 6e83b42d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/06/30 12:04 linux-5.15.y 3dea0e7f549e fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/06/30 09:41 linux-5.15.y 3dea0e7f549e fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/06/30 07:36 linux-5.15.y 3dea0e7f549e fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2025/07/07 12:33 linux-5.15.y 3dea0e7f549e 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in __loop_clr_fd
2025/07/07 08:58 linux-5.15.y 3dea0e7f549e 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in __loop_clr_fd
2025/07/07 02:38 linux-5.15.y 3dea0e7f549e 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in __loop_clr_fd
2025/07/06 20:38 linux-5.15.y 3dea0e7f549e 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in __loop_clr_fd
2025/07/06 12:44 linux-5.15.y 3dea0e7f549e 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in __loop_clr_fd
2025/07/05 22:17 linux-5.15.y 3dea0e7f549e 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in __loop_clr_fd
2025/07/05 06:17 linux-5.15.y 3dea0e7f549e d869b261 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in __loop_clr_fd
2025/07/04 21:25 linux-5.15.y 3dea0e7f549e d869b261 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in __loop_clr_fd
2025/07/03 20:25 linux-5.15.y 3dea0e7f549e 115ceea7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in __loop_clr_fd
2025/07/02 23:23 linux-5.15.y 3dea0e7f549e bc80e4f0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in __loop_clr_fd
2025/07/01 22:12 linux-5.15.y 3dea0e7f549e 091a06cd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in __loop_clr_fd
2025/07/01 15:22 linux-5.15.y 3dea0e7f549e 091a06cd .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.