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: 497d, last: 2h12m
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

  
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 982d 1107d 20/27 fixed on 2021/11/10 00:50
upstream possible deadlock in __loop_clr_fd block 2 1218d 1214d 0/27 auto-closed as invalid on 2021/05/18 10:52
upstream possible deadlock in __loop_clr_fd (3) block 2972 918d 981d 20/27 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:
F2FS-fs (loop0): invalid crc value
F2FS-fs (loop0): Found nat_bits in checkpoint
F2FS-fs (loop0): Try to recover 1th superblock, ret: 0
F2FS-fs (loop0): Mounted with checkpoint version = 753bd00b
======================================================
WARNING: possible circular locking dependency detected
5.15.159-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor212/3500 is trying to acquire lock:
ffff888015dcf138 ((wq_completion)loop0){+.+.}-{0:0}, at: flush_workqueue+0x154/0x1610 kernel/workqueue.c:2830

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

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #7 (&lo->lo_mutex){+.+.}-{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_killable_nested+0x17/0x20 kernel/locking/mutex.c:758
       lo_open+0x68/0x100 drivers/block/loop.c:2055
       blkdev_get_whole+0x94/0x390 block/bdev.c:669
       blkdev_get_by_dev+0x2bc/0xa50 block/bdev.c:824
       blkdev_open+0x138/0x2d0 block/fops.c:463
       do_dentry_open+0x807/0xfb0 fs/open.c:826
       do_open fs/namei.c:3608 [inline]
       path_openat+0x2705/0x2f20 fs/namei.c:3742
       do_filp_open+0x21c/0x460 fs/namei.c:3769
       do_sys_openat2+0x13b/0x500 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+0x243/0x290 fs/open.c:1280
       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

-> #6 (&disk->open_mutex){+.+.}-{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
       blkdev_get_by_dev+0x14d/0xa50 block/bdev.c:817
       swsusp_check+0xb1/0x2c0 kernel/power/swap.c:1526
       software_resume+0xc6/0x3c0 kernel/power/hibernate.c:977
       resume_store+0xe3/0x130 kernel/power/hibernate.c:1179
       kernfs_fop_write_iter+0x3a2/0x4f0 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+0xacf/0xe50 fs/read_write.c:594
       ksys_write+0x1a2/0x2c0 fs/read_write.c:647
       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

-> #5 (system_transition_mutex/1){+.+.}-{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
       software_resume+0x7c/0x3c0 kernel/power/hibernate.c:932
       resume_store+0xe3/0x130 kernel/power/hibernate.c:1179
       kernfs_fop_write_iter+0x3a2/0x4f0 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+0xacf/0xe50 fs/read_write.c:594
       ksys_write+0x1a2/0x2c0 fs/read_write.c:647
       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

-> #4 (&of->mutex){+.+.}-{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
       kernfs_seq_start+0x50/0x3b0 fs/kernfs/file.c:112
       seq_read_iter+0x3d0/0xd10 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+0xa9f/0xe10 fs/read_write.c:485
       ksys_read+0x1a2/0x2c0 fs/read_write.c:623
       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

-> #3 (&p->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
       seq_read_iter+0xae/0xd10 fs/seq_file.c:182
       proc_reg_read_iter+0x1b7/0x280 fs/proc/inode.c:300
       call_read_iter include/linux/fs.h:2166 [inline]
       generic_file_splice_read+0x4ad/0x790 fs/splice.c:311
       do_splice_to fs/splice.c:796 [inline]
       splice_direct_to_actor+0x448/0xc10 fs/splice.c:870
       do_splice_direct+0x285/0x3d0 fs/splice.c:979
       do_sendfile+0x625/0xff0 fs/read_write.c:1249
       __do_sys_sendfile64 fs/read_write.c:1317 [inline]
       __se_sys_sendfile64+0x178/0x1e0 fs/read_write.c:1303
       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

-> #2 (sb_writers#3){.+.+}-{0:0}:
       lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
       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:3037 [inline]
       lo_write_bvec+0x1a3/0x740 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:2234 [inline]
       loop_process_work+0x2309/0x2af0 drivers/block/loop.c:2274
       process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
       worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
       kthread+0x3f6/0x4f0 kernel/kthread.c:334
       ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:300

-> #1 ((work_completion)(&lo->rootcg_work)){+.+.}-{0:0}:
       lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
       process_one_work+0x7f1/0x10c0 kernel/workqueue.c:2286
       worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
       kthread+0x3f6/0x4f0 kernel/kthread.c:334
       ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:300

-> #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+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
       flush_workqueue+0x170/0x1610 kernel/workqueue.c:2830
       drain_workqueue+0xc5/0x390 kernel/workqueue.c:2995
       destroy_workqueue+0x7b/0xae0 kernel/workqueue.c:4439
       __loop_clr_fd+0x241/0xbe0 drivers/block/loop.c:1383
       blkdev_put_whole block/bdev.c:692 [inline]
       blkdev_put+0x455/0x790 block/bdev.c:954
       kill_f2fs_super+0x2ff/0x3c0 fs/f2fs/super.c:4539
       deactivate_locked_super+0xa0/0x110 fs/super.c:335
       cleanup_mnt+0x44e/0x500 fs/namespace.c:1143
       task_work_run+0x129/0x1a0 kernel/task_work.c:164
       exit_task_work include/linux/task_work.h:32 [inline]
       do_exit+0x6a3/0x2480 kernel/exit.c:872
       do_group_exit+0x144/0x310 kernel/exit.c:994
       __do_sys_exit_group kernel/exit.c:1005 [inline]
       __se_sys_exit_group kernel/exit.c:1003 [inline]
       __x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1003
       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:
  (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-executor212/3500:
 #0: ffff88801b59c118 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xfb/0x790 block/bdev.c:912
 #1: ffff88801b58f468 (&lo->lo_mutex){+.+.}-{3:3}, at: __loop_clr_fd+0xa9/0xbe0 drivers/block/loop.c:1365

stack backtrace:
CPU: 0 PID: 3500 Comm: syz-executor212 Not tainted 5.15.159-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/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
 flush_workqueue+0x170/0x1610 kernel/workqueue.c:2830
 drain_workqueue+0xc5/0x390 kernel/workqueue.c:2995
 destroy_workqueue+0x7b/0xae0 kernel/workqueue.c:4439
 __loop_clr_fd+0x241/0xbe0 drivers/block/loop.c:1383
 blkdev_put_whole block/bdev.c:692 [inline]
 blkdev_put+0x455/0x790 block/bdev.c:954
 kill_f2fs_super+0x2ff/0x3c0 fs/f2fs/super.c:4539
 deactivate_locked_super+0xa0/0x110 fs/super.c:335
 cleanup_mnt+0x44e/0x500 fs/namespace.c:1143
 task_work_run+0x129/0x1a0 kernel/task_work.c:164
 exit_task_work include/linux/task_work.h:32 [inline]
 do_exit+0x6a3/0x2480 kernel/exit.c:872
 do_group_exit+0x144/0x310 kernel/exit.c:994
 __do_sys_exit_group kernel/exit.c:1005 [inline]
 __se_sys_exit_group kernel/exit.c:1003 [inline]
 __x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1003
 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:0x7f09879e1b49
Code: Unable to access opcode bytes at RIP 0x7f09879e1b1f.
RSP: 002b:00007ffd17f60ca8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f09879e1b49
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 00007f0987a653d0 R08: ffffffffffffffb8 R09: 0000555555661378
R10: 0000000000000003 R11: 0000000000000246 R12: 00007f0987a653d0
R13: 0000000000000000 R14: 00007f0987a66140 R15: 00007f09879afe20
 </TASK>

Crashes (830):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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
2024/07/19 11:14 linux-5.15.y 7c6d66f0266f ee4e11c8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/19 06:52 linux-5.15.y 7c6d66f0266f ee4e11c8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/19 04:25 linux-5.15.y 7c6d66f0266f ee4e11c8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/19 03:11 linux-5.15.y 7c6d66f0266f ee4e11c8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/19 01:37 linux-5.15.y 7c6d66f0266f ee4e11c8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/19 01:33 linux-5.15.y 7c6d66f0266f ee4e11c8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/18 16:07 linux-5.15.y 7c6d66f0266f 71884c12 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/18 15:04 linux-5.15.y 7c6d66f0266f 71884c12 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/18 13:51 linux-5.15.y 7c6d66f0266f 71884c12 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/18 12:13 linux-5.15.y 7c6d66f0266f 0f902625 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/18 00:28 linux-5.15.y f45bea23c39c 0f902625 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/18 00:28 linux-5.15.y f45bea23c39c 0f902625 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/17 22:45 linux-5.15.y f45bea23c39c 0f902625 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/17 20:44 linux-5.15.y f45bea23c39c 0f902625 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/17 13:59 linux-5.15.y f45bea23c39c 215bec2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/17 07:25 linux-5.15.y f45bea23c39c 215bec2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/17 04:16 linux-5.15.y f45bea23c39c 215bec2d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/16 22:08 linux-5.15.y f45bea23c39c b66b37bd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/16 19:12 linux-5.15.y f45bea23c39c b66b37bd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/16 17:49 linux-5.15.y f45bea23c39c b66b37bd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/16 14:51 linux-5.15.y f45bea23c39c b66b37bd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/16 13:27 linux-5.15.y f45bea23c39c b66b37bd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/16 01:16 linux-5.15.y f45bea23c39c e8709b21 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/15 23:35 linux-5.15.y f45bea23c39c e8709b21 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/15 21:33 linux-5.15.y f45bea23c39c e8709b21 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/15 20:23 linux-5.15.y f45bea23c39c e8709b21 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/15 20:15 linux-5.15.y f45bea23c39c e8709b21 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/15 13:18 linux-5.15.y f45bea23c39c c605e6a2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/15 12:04 linux-5.15.y f45bea23c39c c605e6a2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/15 10:57 linux-5.15.y f45bea23c39c c605e6a2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/15 09:23 linux-5.15.y f45bea23c39c c605e6a2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/15 07:49 linux-5.15.y f45bea23c39c c605e6a2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/15 04:44 linux-5.15.y f45bea23c39c eaeb5c15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/15 02:12 linux-5.15.y f45bea23c39c eaeb5c15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/15 00:12 linux-5.15.y f45bea23c39c eaeb5c15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/14 22:40 linux-5.15.y f45bea23c39c eaeb5c15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/14 21:20 linux-5.15.y f45bea23c39c eaeb5c15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/14 18:18 linux-5.15.y f45bea23c39c eaeb5c15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/14 09:18 linux-5.15.y f45bea23c39c eaeb5c15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/14 00:34 linux-5.15.y f45bea23c39c eaeb5c15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/13 23:04 linux-5.15.y f45bea23c39c eaeb5c15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/13 18:57 linux-5.15.y f45bea23c39c eaeb5c15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/13 16:19 linux-5.15.y f45bea23c39c eaeb5c15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/12 19:52 linux-5.15.y f45bea23c39c eaeb5c15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/11 22:30 linux-5.15.y f45bea23c39c eaeb5c15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/11 21:14 linux-5.15.y f45bea23c39c eaeb5c15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in __loop_clr_fd
2024/07/03 20:47 linux-5.15.y 4878aadf2d15 f76a75f3 .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.