syzbot


possible deadlock in __f2fs_ioctl (2)

Status: auto-obsoleted due to no activity on 2023/06/02 19:31
Subsystems: f2fs
[Documentation on labels]
Reported-by: syzbot+0d79d79c510d77a7c661@syzkaller.appspotmail.com
First crash: 411d, last: 361d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [f2fs?] possible deadlock in __f2fs_ioctl (2) 0 (1) 2023/01/17 02:57
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 possible deadlock in __f2fs_ioctl 1 82d 82d 0/3 upstream: reported on 2023/12/08 16:22
upstream possible deadlock in __f2fs_ioctl f2fs 17 414d 446d 22/26 fixed on 2023/01/11 16:14

Sample crash report:
F2FS-fs (loop4): Try to recover 1th superblock, ret: 0
F2FS-fs (loop4): Mounted with checkpoint version = 753bd00b
======================================================
WARNING: possible circular locking dependency detected
6.2.0-syzkaller-12485-gf3a2439f20d9 #0 Not tainted
------------------------------------------------------
syz-executor.4/24448 is trying to acquire lock:
ffff888063d12698 (&mm->mmap_lock){++++}-{3:3}, at: __might_fault+0xa9/0x180 mm/memory.c:5624

but task is already holding lock:
ffff888036af8088 (&sbi->sb_lock){++++}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2213 [inline]
ffff888036af8088 (&sbi->sb_lock){++++}-{3:3}, at: f2fs_ioc_get_encryption_pwsalt fs/f2fs/file.c:2350 [inline]
ffff888036af8088 (&sbi->sb_lock){++++}-{3:3}, at: __f2fs_ioctl+0x3864/0xa910 fs/f2fs/file.c:4169

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #5 (&sbi->sb_lock){++++}-{3:3}:
       down_write+0x92/0x200 kernel/locking/rwsem.c:1573
       f2fs_down_write fs/f2fs/f2fs.h:2213 [inline]
       f2fs_handle_error+0x8e/0x220 fs/f2fs/super.c:3920
       f2fs_check_nid_range.part.0+0x4d/0x60 fs/f2fs/node.c:39
       f2fs_check_nid_range fs/f2fs/node.c:2282 [inline]
       add_free_nid.isra.0+0x781/0x940 fs/f2fs/node.c:2289
       scan_nat_page fs/f2fs/node.c:2391 [inline]
       __f2fs_build_free_nids+0x5b5/0xe10 fs/f2fs/node.c:2497
       f2fs_build_free_nids fs/f2fs/node.c:2535 [inline]
       f2fs_build_node_manager+0x2072/0x3000 fs/f2fs/node.c:3320
       f2fs_fill_super+0x39ad/0x8b90 fs/f2fs/super.c:4328
       mount_bdev+0x351/0x410 fs/super.c:1371
       legacy_get_tree+0x109/0x220 fs/fs_context.c:610
       vfs_get_tree+0x8d/0x350 fs/super.c:1501
       do_new_mount fs/namespace.c:3042 [inline]
       path_mount+0x1342/0x1e40 fs/namespace.c:3372
       do_mount fs/namespace.c:3385 [inline]
       __do_sys_mount fs/namespace.c:3594 [inline]
       __se_sys_mount fs/namespace.c:3571 [inline]
       __x64_sys_mount+0x283/0x300 fs/namespace.c:3571
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #4 (&nm_i->nat_tree_lock){++++}-{3:3}:
       down_read+0x3d/0x50 kernel/locking/rwsem.c:1520
       f2fs_down_read fs/f2fs/f2fs.h:2188 [inline]
       f2fs_get_node_info+0x1ac/0x1070 fs/f2fs/node.c:564
       f2fs_do_write_data_page+0x7f5/0x1e50 fs/f2fs/data.c:2727
       f2fs_write_single_data_page+0x147e/0x19c0 fs/f2fs/data.c:2862
       f2fs_write_cache_pages+0xcf2/0x1f00 fs/f2fs/data.c:3145
       __f2fs_write_data_pages fs/f2fs/data.c:3296 [inline]
       f2fs_write_data_pages+0x4c7/0x1300 fs/f2fs/data.c:3323
       do_writepages+0x1a8/0x640 mm/page-writeback.c:2551
       filemap_fdatawrite_wbc mm/filemap.c:390 [inline]
       filemap_fdatawrite_wbc+0x147/0x1b0 mm/filemap.c:380
       __filemap_fdatawrite_range+0xb8/0xf0 mm/filemap.c:423
       file_write_and_wait_range+0xce/0x140 mm/filemap.c:781
       f2fs_do_sync_file+0x3a4/0x2a60 fs/f2fs/file.c:275
       f2fs_sync_file+0x13a/0x190 fs/f2fs/file.c:393
       vfs_fsync_range+0x13e/0x230 fs/sync.c:188
       generic_write_sync include/linux/fs.h:2452 [inline]
       f2fs_file_write_iter+0x185f/0x3270 fs/f2fs/file.c:4721
       call_write_iter include/linux/fs.h:1851 [inline]
       do_iter_readv_writev+0x20b/0x3b0 fs/read_write.c:735
       do_iter_write+0x182/0x700 fs/read_write.c:861
       vfs_iter_write+0x74/0xa0 fs/read_write.c:902
       iter_file_splice_write+0x743/0xc80 fs/splice.c:778
       do_splice_from fs/splice.c:856 [inline]
       direct_splice_actor+0x114/0x180 fs/splice.c:1023
       splice_direct_to_actor+0x335/0x8a0 fs/splice.c:978
       do_splice_direct+0x1ab/0x280 fs/splice.c:1066
       do_sendfile+0xb19/0x12c0 fs/read_write.c:1255
       __do_sys_sendfile64 fs/read_write.c:1323 [inline]
       __se_sys_sendfile64 fs/read_write.c:1309 [inline]
       __x64_sys_sendfile64+0x1d0/0x210 fs/read_write.c:1309
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #3 (&sbi->cp_rwsem){++++}-{3:3}:
       down_read+0x3d/0x50 kernel/locking/rwsem.c:1520
       f2fs_down_read fs/f2fs/f2fs.h:2188 [inline]
       f2fs_lock_op fs/f2fs/f2fs.h:2231 [inline]
       f2fs_zero_range fs/f2fs/file.c:1563 [inline]
       f2fs_fallocate+0x17b5/0x37a0 fs/f2fs/file.c:1839
       vfs_fallocate+0x48b/0xe40 fs/open.c:324
       ksys_fallocate fs/open.c:347 [inline]
       __do_sys_fallocate fs/open.c:355 [inline]
       __se_sys_fallocate fs/open.c:353 [inline]
       __x64_sys_fallocate+0xd3/0x140 fs/open.c:353
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #2 (mapping.invalidate_lock#12){++++}-{3:3}:
       down_read+0x3d/0x50 kernel/locking/rwsem.c:1520
       filemap_invalidate_lock_shared include/linux/fs.h:813 [inline]
       f2fs_vm_page_mkwrite+0x630/0x1cf0 fs/f2fs/file.c:104
       do_page_mkwrite+0x19b/0x680 mm/memory.c:2925
       wp_page_shared mm/memory.c:3274 [inline]
       do_wp_page+0x356/0x3520 mm/memory.c:3356
       handle_pte_fault mm/memory.c:4927 [inline]
       __handle_mm_fault+0x19a1/0x3e60 mm/memory.c:5051
       handle_mm_fault+0x2ba/0x9c0 mm/memory.c:5197
       do_user_addr_fault+0x475/0x1230 arch/x86/mm/fault.c:1407
       handle_page_fault arch/x86/mm/fault.c:1498 [inline]
       exc_page_fault+0x98/0x170 arch/x86/mm/fault.c:1554
       asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570
       copy_user_generic_string+0x30/0x50 arch/x86/lib/copy_user_64.S:132
       copy_user_generic arch/x86/include/asm/uaccess_64.h:37 [inline]
       raw_copy_to_user arch/x86/include/asm/uaccess_64.h:58 [inline]
       _copy_to_user lib/usercopy.c:41 [inline]
       _copy_to_user+0x127/0x150 lib/usercopy.c:34
       copy_to_user include/linux/uaccess.h:169 [inline]
       do_pipe2+0x128/0x1b0 fs/pipe.c:1012
       __do_sys_pipe2 fs/pipe.c:1028 [inline]
       __se_sys_pipe2 fs/pipe.c:1026 [inline]
       __x64_sys_pipe2+0x54/0x80 fs/pipe.c:1026
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #1 (sb_pagefaults#5){.+.+}-{0:0}:
       percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
       __sb_start_write include/linux/fs.h:1477 [inline]
       sb_start_pagefault include/linux/fs.h:1581 [inline]
       f2fs_vm_page_mkwrite+0x48a/0x1cf0 fs/f2fs/file.c:99
       do_page_mkwrite+0x19b/0x680 mm/memory.c:2925
       wp_page_shared mm/memory.c:3274 [inline]
       do_wp_page+0x356/0x3520 mm/memory.c:3356
       handle_pte_fault mm/memory.c:4927 [inline]
       __handle_mm_fault+0x19a1/0x3e60 mm/memory.c:5051
       handle_mm_fault+0x2ba/0x9c0 mm/memory.c:5197
       do_user_addr_fault+0x475/0x1230 arch/x86/mm/fault.c:1407
       handle_page_fault arch/x86/mm/fault.c:1498 [inline]
       exc_page_fault+0x98/0x170 arch/x86/mm/fault.c:1554
       asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570
       copy_user_generic_string+0x30/0x50 arch/x86/lib/copy_user_64.S:132
       copy_user_generic arch/x86/include/asm/uaccess_64.h:37 [inline]
       raw_copy_to_user arch/x86/include/asm/uaccess_64.h:58 [inline]
       _copy_to_user lib/usercopy.c:41 [inline]
       _copy_to_user+0x127/0x150 lib/usercopy.c:34
       copy_to_user include/linux/uaccess.h:169 [inline]
       do_pipe2+0x128/0x1b0 fs/pipe.c:1012
       __do_sys_pipe2 fs/pipe.c:1028 [inline]
       __se_sys_pipe2 fs/pipe.c:1026 [inline]
       __x64_sys_pipe2+0x54/0x80 fs/pipe.c:1026
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #0 (&mm->mmap_lock){++++}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3098 [inline]
       check_prevs_add kernel/locking/lockdep.c:3217 [inline]
       validate_chain kernel/locking/lockdep.c:3832 [inline]
       __lock_acquire+0x2ec7/0x5d40 kernel/locking/lockdep.c:5056
       lock_acquire kernel/locking/lockdep.c:5669 [inline]
       lock_acquire+0x1e3/0x670 kernel/locking/lockdep.c:5634
       __might_fault mm/memory.c:5625 [inline]
       __might_fault+0x10c/0x180 mm/memory.c:5618
       _copy_to_user+0x29/0x150 lib/usercopy.c:36
       copy_to_user include/linux/uaccess.h:169 [inline]
       f2fs_ioc_get_encryption_pwsalt fs/f2fs/file.c:2365 [inline]
       __f2fs_ioctl+0x3994/0xa910 fs/f2fs/file.c:4169
       f2fs_ioctl+0x18e/0x220 fs/f2fs/file.c:4242
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:870 [inline]
       __se_sys_ioctl fs/ioctl.c:856 [inline]
       __x64_sys_ioctl+0x197/0x210 fs/ioctl.c:856
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

other info that might help us debug this:

Chain exists of:
  &mm->mmap_lock --> &nm_i->nat_tree_lock --> &sbi->sb_lock

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&sbi->sb_lock);
                               lock(&nm_i->nat_tree_lock);
                               lock(&sbi->sb_lock);
  lock(&mm->mmap_lock);

 *** DEADLOCK ***

2 locks held by syz-executor.4/24448:
 #0: ffff888039bf0460 (sb_writers#19){.+.+}-{0:0}, at: f2fs_ioc_get_encryption_pwsalt fs/f2fs/file.c:2346 [inline]
 #0: ffff888039bf0460 (sb_writers#19){.+.+}-{0:0}, at: __f2fs_ioctl+0x36a2/0xa910 fs/f2fs/file.c:4169
 #1: ffff888036af8088 (&sbi->sb_lock){++++}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2213 [inline]
 #1: ffff888036af8088 (&sbi->sb_lock){++++}-{3:3}, at: f2fs_ioc_get_encryption_pwsalt fs/f2fs/file.c:2350 [inline]
 #1: ffff888036af8088 (&sbi->sb_lock){++++}-{3:3}, at: __f2fs_ioctl+0x3864/0xa910 fs/f2fs/file.c:4169

stack backtrace:
CPU: 1 PID: 24448 Comm: syz-executor.4 Not tainted 6.2.0-syzkaller-12485-gf3a2439f20d9 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/16/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106
 check_noncircular+0x25f/0x2e0 kernel/locking/lockdep.c:2178
 check_prev_add kernel/locking/lockdep.c:3098 [inline]
 check_prevs_add kernel/locking/lockdep.c:3217 [inline]
 validate_chain kernel/locking/lockdep.c:3832 [inline]
 __lock_acquire+0x2ec7/0x5d40 kernel/locking/lockdep.c:5056
 lock_acquire kernel/locking/lockdep.c:5669 [inline]
 lock_acquire+0x1e3/0x670 kernel/locking/lockdep.c:5634
 __might_fault mm/memory.c:5625 [inline]
 __might_fault+0x10c/0x180 mm/memory.c:5618
 _copy_to_user+0x29/0x150 lib/usercopy.c:36
 copy_to_user include/linux/uaccess.h:169 [inline]
 f2fs_ioc_get_encryption_pwsalt fs/f2fs/file.c:2365 [inline]
 __f2fs_ioctl+0x3994/0xa910 fs/f2fs/file.c:4169
 f2fs_ioctl+0x18e/0x220 fs/f2fs/file.c:4242
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:870 [inline]
 __se_sys_ioctl fs/ioctl.c:856 [inline]
 __x64_sys_ioctl+0x197/0x210 fs/ioctl.c:856
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f32f3e8c0f9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f32f4ca4168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f32f3fabf80 RCX: 00007f32f3e8c0f9
RDX: 0000000000000000 RSI: 0000000040106614 RDI: 0000000000000004
RBP: 00007f32f3ee7ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffee64da7df R14: 00007f32f4ca4300 R15: 0000000000022000
 </TASK>

Crashes (84):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/02/27 13:12 upstream f3a2439f20d9 e792ae78 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root possible deadlock in __f2fs_ioctl
2023/02/22 20:47 upstream 5b7c4cabbb65 409945bc .config console log report info ci-upstream-kasan-gce-smack-root possible deadlock in __f2fs_ioctl
2023/02/21 16:27 upstream 89f5349e0673 f949448d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/20 19:28 upstream c9c3395d5e3d 2414209c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/20 13:33 upstream c9c3395d5e3d bcdf85f8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/18 22:14 upstream 5e725d112e1a d02e9a70 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/17 12:14 upstream ec35307e18ba 3e7039f4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/17 07:28 upstream 3ac88fa4605e 851bc19a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/15 15:19 upstream e1c04510f521 6be0f1f5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/14 23:22 upstream 82eac0c830b7 e62ba3c1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/14 19:12 upstream 82eac0c830b7 e62ba3c1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/14 10:22 upstream f6feea56f66d 93ae7e0a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/13 11:17 upstream ceaa837f96ad 957959cb .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/12 23:08 upstream 711e9a4d52bf 93e26d60 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/12 19:27 upstream f339c2597ebb 93e26d60 .config console log report info ci-upstream-kasan-gce-smack-root possible deadlock in __f2fs_ioctl
2023/02/12 15:16 upstream f339c2597ebb 93e26d60 .config console log report info ci-upstream-kasan-gce-smack-root possible deadlock in __f2fs_ioctl
2023/02/12 09:43 upstream f339c2597ebb 93e26d60 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/11 21:04 upstream d12aca5c0cee 93e26d60 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/11 14:56 upstream 420b2d431d18 93e26d60 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/09 19:36 upstream 35674e787518 07980f9d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/09 16:00 upstream 0983f6bf2bfc 07980f9d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/09 14:04 upstream 0983f6bf2bfc 14a312c8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/09 11:38 upstream 0983f6bf2bfc 14a312c8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/09 03:14 upstream 0983f6bf2bfc 14a312c8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/08 20:24 upstream 0983f6bf2bfc fc9c934e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/08 12:36 upstream 0983f6bf2bfc abbb67b7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/08 10:37 upstream 0983f6bf2bfc 15c3d445 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/08 01:51 upstream 513c1a3d3f19 15c3d445 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/07 20:35 upstream 513c1a3d3f19 15c3d445 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/07 07:06 upstream 05ecb680708a 5bc3be51 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/06 13:44 upstream d2d11f342b17 0a9c11b6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/05 17:44 upstream 837c07cf68fe be607b78 .config console log report info ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/05 15:51 upstream 837c07cf68fe be607b78 .config console log report info ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/05 05:57 upstream db27c22251e7 be607b78 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/04 21:17 upstream db27c22251e7 be607b78 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/04 15:05 upstream 0136d86b7852 be607b78 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/04 07:04 upstream 0136d86b7852 1b2f701a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/03 03:18 upstream e7368fd30165 33fc5c09 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/02 14:32 upstream 9f266ccaa2f5 16d19e30 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/02 02:41 upstream 9f266ccaa2f5 9a6f477c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/02/01 21:53 upstream c0b67534c95c 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root possible deadlock in __f2fs_ioctl
2023/01/25 00:46 upstream fb6e71db53f3 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/01/24 17:40 upstream 7bf70dbb1882 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/01/22 22:11 upstream 2475bf0250de cc0f9968 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/01/22 20:47 upstream 2241ab53cbb5 cc0f9968 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/01/21 16:18 upstream f883675bf652 cc0f9968 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/01/21 16:00 upstream f883675bf652 cc0f9968 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/01/21 01:22 upstream edc00350d205 cc0f9968 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/01/20 23:13 upstream edc00350d205 dd15ff29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/01/17 17:31 upstream 6e50979a9c87 42660d9e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/01/16 20:58 upstream 5dc4c995db9e a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/01/15 04:17 upstream 97ec4d559d93 a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/01/13 15:21 upstream d9fc1511728c 529798b0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/01/13 02:50 upstream e8f60cd7db24 96166539 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs possible deadlock in __f2fs_ioctl
2023/03/04 19:30 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 596b6b709632 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in __f2fs_ioctl
2023/02/27 18:15 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2ebd1fbb946d e792ae78 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in __f2fs_ioctl
2023/02/26 11:04 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2ebd1fbb946d ee50e71c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in __f2fs_ioctl
2023/02/19 01:00 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 2d3827b3f393 bcdf85f8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in __f2fs_ioctl
2023/02/05 11:38 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci ca72d58361ee be607b78 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in __f2fs_ioctl
2023/02/04 02:47 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci ca72d58361ee 1b2f701a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in __f2fs_ioctl
2023/01/23 07:03 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci edb2f0dc90f2 44388686 .config console log report info ci-upstream-gce-arm64 possible deadlock in __f2fs_ioctl
2023/01/19 10:13 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 9598c377d828 42660d9e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 possible deadlock in __f2fs_ioctl
* Struck through repros no longer work on HEAD.