syzbot


possible deadlock in ntfs_mark_rec_free

Status: auto-obsoleted due to no activity on 2024/03/07 08:53
Subsystems: ntfs3
[Documentation on labels]
Reported-by: syzbot+f83f0dbef763c426e3cf@syzkaller.appspotmail.com
First crash: 641d, last: 282d
Discussions (10)
Title Replies (including bot) Last reply
[syzbot] Monthly ntfs3 report (Jan 2024) 0 (1) 2024/01/02 13:36
[syzbot] Monthly ntfs3 report (Oct 2023) 0 (1) 2023/11/01 10:13
[syzbot] Monthly ntfs3 report (Sep 2023) 0 (1) 2023/10/02 09:42
[syzbot] Monthly ntfs3 report (Aug 2023) 0 (1) 2023/08/30 12:45
[syzbot] Monthly ntfs3 report (Jul 2023) 0 (1) 2023/07/30 13:16
[syzbot] Monthly ntfs3 report (Jun 2023) 0 (1) 2023/06/29 09:21
[syzbot] Monthly ntfs3 report (May 2023) 0 (1) 2023/05/29 08:47
[syzbot] Monthly ntfs3 report (Apr 2023) 0 (1) 2023/04/28 08:47
[syzbot] Monthly ntfs3 report 0 (1) 2023/03/27 17:38
[syzbot] [ntfs3?] possible deadlock in ntfs_mark_rec_free 0 (1) 2023/01/03 12:45
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 possible deadlock in ntfs_mark_rec_free 16 353d 561d 0/3 auto-obsoleted due to no activity on 2024/01/25 16:19
upstream possible deadlock in ntfs_mark_rec_free (2) ntfs3 C done 87 2d06h 158d 0/28 upstream: reported C repro on 2024/04/30 03:29
linux-6.1 possible deadlock in ntfs_mark_rec_free (2) 12 138d 141d 0/3 auto-obsoleted due to no activity on 2024/07/29 08:57
linux-5.15 possible deadlock in ntfs_mark_rec_free origin:upstream C error 17 136d 141d 0/3 upstream: reported C repro on 2024/05/17 04:58

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
6.7.0-rc7-syzkaller-00016-gf5837722ffec #0 Not tainted
------------------------------------------------------
udevd/4511 is trying to acquire lock:
ffff88820ade2120 (&wnd->rw_lock/1){+.+.}-{3:3}, at: ntfs_mark_rec_free+0x3f/0x2b0 fs/ntfs3/fsntfs.c:742

but task is already holding lock:
ffffffff8da12c80 (fs_reclaim){+.+.}-{0:0}, at: __perform_reclaim mm/page_alloc.c:3766 [inline]
ffffffff8da12c80 (fs_reclaim){+.+.}-{0:0}, at: __alloc_pages_direct_reclaim mm/page_alloc.c:3791 [inline]
ffffffff8da12c80 (fs_reclaim){+.+.}-{0:0}, at: __alloc_pages_slowpath+0xd01/0x23a0 mm/page_alloc.c:4196

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (fs_reclaim){+.+.}-{0:0}:
       lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754
       __fs_reclaim_acquire mm/page_alloc.c:3693 [inline]
       fs_reclaim_acquire+0x87/0x120 mm/page_alloc.c:3707
       might_alloc include/linux/sched/mm.h:303 [inline]
       slab_pre_alloc_hook mm/slab.h:710 [inline]
       slab_alloc_node mm/slub.c:3460 [inline]
       __kmem_cache_alloc_node+0x3e/0x300 mm/slub.c:3517
       __do_kmalloc_node mm/slab_common.c:1006 [inline]
       __kmalloc_node+0xa2/0x190 mm/slab_common.c:1014
       kmalloc_node include/linux/slab.h:620 [inline]
       kvmalloc_node+0x72/0x180 mm/util.c:617
       kvmalloc include/linux/slab.h:738 [inline]
       run_add_entry+0x9ea/0xe70 fs/ntfs3/run.c:389
       attr_allocate_clusters+0x3ab/0x990 fs/ntfs3/attrib.c:181
       attr_set_size+0x2049/0x4290 fs/ntfs3/attrib.c:572
       ntfs_set_size+0x161/0x1f0 fs/ntfs3/inode.c:840
       ntfs_extend+0x16d/0x4a0 fs/ntfs3/file.c:333
       ntfs_file_write_iter+0x308/0x6e0 fs/ntfs3/file.c:1077
       call_write_iter include/linux/fs.h:2020 [inline]
       new_sync_write fs/read_write.c:491 [inline]
       vfs_write+0x792/0xb20 fs/read_write.c:584
       ksys_write+0x1a0/0x2c0 fs/read_write.c:637
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0x45/0x110 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x63/0x6b

-> #1 (&ni->file.run_lock#2){++++}-{3:3}:
       lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754
       down_read+0xb1/0xa40 kernel/locking/rwsem.c:1526
       mi_read+0x181/0x5a0 fs/ntfs3/record.c:129
       mi_format_new+0x1ab/0x5d0 fs/ntfs3/record.c:420
       ni_add_subrecord+0xe2/0x430 fs/ntfs3/frecord.c:372
       ntfs_look_free_mft+0x878/0x10c0 fs/ntfs3/fsntfs.c:715
       ni_create_attr_list+0x9bd/0x1480 fs/ntfs3/frecord.c:876
       ni_ins_attr_ext+0x365/0xbe0 fs/ntfs3/frecord.c:974
       ni_insert_attr fs/ntfs3/frecord.c:1141 [inline]
       ni_insert_resident fs/ntfs3/frecord.c:1525 [inline]
       ni_add_name+0x809/0xe90 fs/ntfs3/frecord.c:3047
       ntfs_link_inode+0x130/0x170 fs/ntfs3/inode.c:1730
       ntfs_link+0x116/0x250 fs/ntfs3/namei.c:156
       vfs_link+0x4ed/0x680 fs/namei.c:4588
       do_linkat+0x356/0x750 fs/namei.c:4659
       __do_sys_link fs/namei.c:4693 [inline]
       __se_sys_link fs/namei.c:4691 [inline]
       __x64_sys_link+0x86/0x90 fs/namei.c:4691
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0x45/0x110 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x63/0x6b

-> #0 (&wnd->rw_lock/1){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3134 [inline]
       check_prevs_add kernel/locking/lockdep.c:3253 [inline]
       validate_chain+0x1909/0x5ab0 kernel/locking/lockdep.c:3869
       __lock_acquire+0x1345/0x1fd0 kernel/locking/lockdep.c:5137
       lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754
       down_write_nested+0x3d/0x50 kernel/locking/rwsem.c:1695
       ntfs_mark_rec_free+0x3f/0x2b0 fs/ntfs3/fsntfs.c:742
       ni_delete_all+0x8ad/0x980 fs/ntfs3/frecord.c:1637
       ni_clear+0x36e/0x3f0 fs/ntfs3/frecord.c:106
       evict+0x2a4/0x630 fs/inode.c:666
       __dentry_kill+0x436/0x660 fs/dcache.c:607
       shrink_dentry_list+0x3dd/0x700 fs/dcache.c:1201
       prune_dcache_sb+0x10f/0x170 fs/dcache.c:1282
       super_cache_scan+0x345/0x4a0 fs/super.c:228
       do_shrink_slab+0x6ed/0x1130 mm/shrinker.c:435
       shrink_slab_memcg mm/shrinker.c:548 [inline]
       shrink_slab+0x883/0x14c0 mm/shrinker.c:626
       shrink_node_memcgs mm/vmscan.c:5844 [inline]
       shrink_node+0x11d6/0x28c0 mm/vmscan.c:5877
       shrink_zones mm/vmscan.c:6116 [inline]
       do_try_to_free_pages+0x717/0x19e0 mm/vmscan.c:6178
       try_to_free_pages+0x9df/0x1000 mm/vmscan.c:6413
       __perform_reclaim mm/page_alloc.c:3769 [inline]
       __alloc_pages_direct_reclaim mm/page_alloc.c:3791 [inline]
       __alloc_pages_slowpath+0xdaa/0x23a0 mm/page_alloc.c:4196
       __alloc_pages+0x413/0x680 mm/page_alloc.c:4581
       alloc_pages_mpol+0x3de/0x640 mm/mempolicy.c:2133
       alloc_pages mm/mempolicy.c:2204 [inline]
       folio_alloc+0x12a/0x330 mm/mempolicy.c:2211
       filemap_alloc_folio+0xde/0x500 mm/filemap.c:974
       __filemap_get_folio+0x431/0xbb0 mm/filemap.c:1918
       filemap_fault+0xb10/0x1670 mm/filemap.c:3252
       __do_fault+0x133/0x4e0 mm/memory.c:4266
       do_read_fault mm/memory.c:4629 [inline]
       do_fault mm/memory.c:4763 [inline]
       do_pte_missing mm/memory.c:3731 [inline]
       handle_pte_fault mm/memory.c:5039 [inline]
       __handle_mm_fault mm/memory.c:5180 [inline]
       handle_mm_fault+0x4c9b/0x6680 mm/memory.c:5345
       do_user_addr_fault arch/x86/mm/fault.c:1364 [inline]
       handle_page_fault arch/x86/mm/fault.c:1505 [inline]
       exc_page_fault+0x456/0x870 arch/x86/mm/fault.c:1561
       asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570

other info that might help us debug this:

Chain exists of:
  &wnd->rw_lock/1 --> &ni->file.run_lock#2 --> fs_reclaim

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(fs_reclaim);
                               lock(&ni->file.run_lock#2);
                               lock(fs_reclaim);
  lock(&wnd->rw_lock/1);

 *** DEADLOCK ***

3 locks held by udevd/4511:
 #0: ffff88801e7b0fa0 (mapping.invalidate_lock){++++}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:857 [inline]
 #0: ffff88801e7b0fa0 (mapping.invalidate_lock){++++}-{3:3}, at: filemap_fault+0xac7/0x1670 mm/filemap.c:3249
 #1: ffffffff8da12c80 (fs_reclaim){+.+.}-{0:0}, at: __perform_reclaim mm/page_alloc.c:3766 [inline]
 #1: ffffffff8da12c80 (fs_reclaim){+.+.}-{0:0}, at: __alloc_pages_direct_reclaim mm/page_alloc.c:3791 [inline]
 #1: ffffffff8da12c80 (fs_reclaim){+.+.}-{0:0}, at: __alloc_pages_slowpath+0xd01/0x23a0 mm/page_alloc.c:4196
 #2: ffff88820ade00e0 (&type->s_umount_key#62){++++}-{3:3}, at: super_trylock_shared fs/super.c:610 [inline]
 #2: ffff88820ade00e0 (&type->s_umount_key#62){++++}-{3:3}, at: super_cache_scan+0x94/0x4a0 fs/super.c:203

stack backtrace:
CPU: 0 PID: 4511 Comm: udevd Not tainted 6.7.0-rc7-syzkaller-00016-gf5837722ffec #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
 check_noncircular+0x366/0x490 kernel/locking/lockdep.c:2187
 check_prev_add kernel/locking/lockdep.c:3134 [inline]
 check_prevs_add kernel/locking/lockdep.c:3253 [inline]
 validate_chain+0x1909/0x5ab0 kernel/locking/lockdep.c:3869
 __lock_acquire+0x1345/0x1fd0 kernel/locking/lockdep.c:5137
 lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754
 down_write_nested+0x3d/0x50 kernel/locking/rwsem.c:1695
 ntfs_mark_rec_free+0x3f/0x2b0 fs/ntfs3/fsntfs.c:742
 ni_delete_all+0x8ad/0x980 fs/ntfs3/frecord.c:1637
 ni_clear+0x36e/0x3f0 fs/ntfs3/frecord.c:106
 evict+0x2a4/0x630 fs/inode.c:666
 __dentry_kill+0x436/0x660 fs/dcache.c:607
 shrink_dentry_list+0x3dd/0x700 fs/dcache.c:1201
 prune_dcache_sb+0x10f/0x170 fs/dcache.c:1282
 super_cache_scan+0x345/0x4a0 fs/super.c:228
 do_shrink_slab+0x6ed/0x1130 mm/shrinker.c:435
 shrink_slab_memcg mm/shrinker.c:548 [inline]
 shrink_slab+0x883/0x14c0 mm/shrinker.c:626
 shrink_node_memcgs mm/vmscan.c:5844 [inline]
 shrink_node+0x11d6/0x28c0 mm/vmscan.c:5877
 shrink_zones mm/vmscan.c:6116 [inline]
 do_try_to_free_pages+0x717/0x19e0 mm/vmscan.c:6178
 try_to_free_pages+0x9df/0x1000 mm/vmscan.c:6413
 __perform_reclaim mm/page_alloc.c:3769 [inline]
 __alloc_pages_direct_reclaim mm/page_alloc.c:3791 [inline]
 __alloc_pages_slowpath+0xdaa/0x23a0 mm/page_alloc.c:4196
 __alloc_pages+0x413/0x680 mm/page_alloc.c:4581
 alloc_pages_mpol+0x3de/0x640 mm/mempolicy.c:2133
 alloc_pages mm/mempolicy.c:2204 [inline]
 folio_alloc+0x12a/0x330 mm/mempolicy.c:2211
 filemap_alloc_folio+0xde/0x500 mm/filemap.c:974
 __filemap_get_folio+0x431/0xbb0 mm/filemap.c:1918
 filemap_fault+0xb10/0x1670 mm/filemap.c:3252
 __do_fault+0x133/0x4e0 mm/memory.c:4266
 do_read_fault mm/memory.c:4629 [inline]
 do_fault mm/memory.c:4763 [inline]
 do_pte_missing mm/memory.c:3731 [inline]
 handle_pte_fault mm/memory.c:5039 [inline]
 __handle_mm_fault mm/memory.c:5180 [inline]
 handle_mm_fault+0x4c9b/0x6680 mm/memory.c:5345
 do_user_addr_fault arch/x86/mm/fault.c:1364 [inline]
 handle_page_fault arch/x86/mm/fault.c:1505 [inline]
 exc_page_fault+0x456/0x870 arch/x86/mm/fault.c:1561
 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570
RIP: 0033:0x55c9f70729ba
Code: Unable to access opcode bytes at 0x55c9f7072990.
RSP: 002b:00007fff3fde5b20 EFLAGS: 00010207
RAX: 0000000000000000 RBX: 000055c9f70926c8 RCX: 00007f60c29165f4
RDX: 00007fff3fde5b28 RSI: 000055c9f7082897 RDI: 00000000ffffff9c
RBP: 000055c9f901bfb8 R08: 0000000000000000 R09: 00007fff3fdeb0b0
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 0005f9c4c6fe15c0 R15: 000055c9f7086dca
 </TASK>

Crashes (826):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/12/28 08:52 upstream f5837722ffec fb427a07 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/19 11:16 upstream dd72f9c7e512 42e1d524 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/19 05:26 upstream dd72f9c7e512 342b9c55 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/19 00:02 upstream dd72f9c7e512 342b9c55 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/18 18:05 upstream dd72f9c7e512 342b9c55 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/18 10:10 upstream 06dc10eae55b 342b9c55 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in ntfs_mark_rec_free
2023/10/18 01:06 upstream 06dc10eae55b 342b9c55 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/17 18:13 upstream 213f891525c2 342b9c55 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/17 00:26 upstream 58720809f527 342b9c55 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/16 10:23 upstream 58720809f527 f757a323 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/15 21:10 upstream fbe1bf1e5ff1 f757a323 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/15 19:04 upstream 9a3dad63edbe f757a323 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/15 06:26 upstream 70f8c6f8f880 f757a323 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/14 18:30 upstream 70f8c6f8f880 f757a323 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/14 04:45 upstream 8cb1f10d8c4b f757a323 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/13 11:26 upstream 10a6e5feccb8 6388bc36 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/13 09:35 upstream e8c127b05766 6388bc36 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/10 01:55 upstream 94f6f0550c62 c9be5398 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/09 05:05 upstream 37faf07bf90a 5e837c76 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/08 19:35 upstream 37faf07bf90a 5e837c76 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/08 16:10 upstream b9ddbb0cde2a 5e837c76 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/08 09:18 upstream b9ddbb0cde2a 5e837c76 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/07 15:18 upstream 82714078aee4 5e837c76 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/07 05:36 upstream 82714078aee4 5e837c76 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/06 14:33 upstream b78b18fb8ee1 ea12a918 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/06 12:51 upstream b78b18fb8ee1 db17ad9f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/05 18:30 upstream 3006adf3be79 db17ad9f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/04 12:11 upstream cbf3a2cb156a b7d7ff54 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/04 07:54 upstream cbf3a2cb156a 65faba36 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/03 18:46 upstream 5e62ed3b1c8a 65faba36 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/03 02:01 upstream ce36c8b14987 65faba36 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/01 23:30 upstream e81a2dabc3f3 8e26a358 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/10/01 19:55 upstream e402b08634b3 8e26a358 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root possible deadlock in ntfs_mark_rec_free
2023/09/30 15:14 upstream 9f3ebbef746f 8e26a358 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/09/29 23:49 upstream 71e58659bfc0 8e26a358 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root possible deadlock in ntfs_mark_rec_free
2023/09/26 13:15 upstream 6465e260f487 0b6a67ac .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/09/26 00:15 upstream 6465e260f487 0b6a67ac .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/09/24 22:34 upstream 6465e260f487 0b6a67ac .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/09/24 00:05 upstream d90b0276af8f 0b6a67ac .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/09/22 23:17 upstream 8018e02a8703 0b6a67ac .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/09/21 20:56 upstream b5cbe7c00aa0 0b6a67ac .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/08/28 05:08 upstream 2dde18cd1d8f 7ba13a15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/08/27 11:13 upstream 28f20a19294d 7ba13a15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/08/27 09:28 upstream 3b35375f19fe 7ba13a15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/08/27 08:21 upstream 3b35375f19fe 7ba13a15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/08/27 05:21 upstream 3b35375f19fe 7ba13a15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/08/26 16:58 upstream 382d4cd18475 7ba13a15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/08/26 05:36 upstream 382d4cd18475 7ba13a15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/08/26 00:54 upstream 382d4cd18475 03d9c195 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/08/24 14:02 upstream 93f5de5f648d 4d7ae7ab .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in ntfs_mark_rec_free
2023/08/22 21:09 upstream 53663f4103ff b81ca3f6 .config console log report info ci-upstream-kasan-gce-smack-root possible deadlock in ntfs_mark_rec_free
2023/08/13 09:54 upstream a785fd28d31f 39990d51 .config console log report info ci-qemu-upstream possible deadlock in ntfs_mark_rec_free
2023/01/03 12:21 upstream 69b41ac87e4a d43e0eb8 .config console log report info ci-qemu-upstream possible deadlock in ntfs_mark_rec_free
2023/01/02 21:45 upstream 88603b6dc419 ab32d508 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in ntfs_mark_rec_free
2023/06/15 09:31 upstream b6dad5178cea ee64538c .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu-upstream-386 possible deadlock in ntfs_mark_rec_free
2023/05/24 21:41 linux-next 715abedee4cd 4bce1a3e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root possible deadlock in ntfs_mark_rec_free
* Struck through repros no longer work on HEAD.