syzbot


possible deadlock in ocfs2_remap_file_range

Status: upstream: reported C repro on 2024/10/03 12:41
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+5efec5fd20aea7f08df7@syzkaller.appspotmail.com
First crash: 209d, last: 2d23h
Fix commit to backport (bisect log) :
tree: upstream
commit 7bf1823e010e8db2fb649c790bd1b449a75f52d8
Author: Mohammed Anees <pvmohammedanees2003@gmail.com>
Date: Tue Sep 24 09:32:57 2024 +0000

  ocfs2: fix deadlock in ocfs2_get_system_file_inode

  
Bug presence (2)
Date Name Commit Repro Result
2024/10/29 linux-5.15.y (ToT) 74cdd62cb470 C [report] possible deadlock in ocfs2_get_system_file_inode
2024/10/29 upstream (ToT) e42b1a9a2557 C Didn't crash
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 possible deadlock in ocfs2_remap_file_range origin:lts-only C done 47 4d18h 178d 0/3 upstream: reported C repro on 2024/11/03 05:20
Last patch testing requests (4)
Created Duration User Patch Repo Result
2025/04/17 12:41 13m retest repro linux-5.15.y report log
2025/04/17 12:41 12m retest repro linux-5.15.y report log
2025/02/02 23:57 9m retest repro linux-5.15.y report log
2025/02/02 23:57 12m retest repro linux-5.15.y report log
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2025/04/13 12:38 6h40m fix candidate upstream OK (1) job log

Sample crash report:
loop0: detected capacity change from 0 to 32768
ocfs2: Mounting device (7,0) on (node local, slot 0) with ordered data mode.
======================================================
WARNING: possible circular locking dependency detected
5.15.176-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor423/4312 is trying to acquire lock:
ffff8880703294a0 (&ocfs2_file_ip_alloc_sem_key/1){+.+.}-{3:3}, at: ocfs2_remap_file_range+0x488/0x8d0 fs/ocfs2/file.c:2698

but task is already holding lock:
ffff88807032a2e0 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_remap_file_range+0x45c/0x8d0 fs/ocfs2/file.c:2696

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}:
       lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
       down_read+0x45/0x2e0 kernel/locking/rwsem.c:1498
       ocfs2_read_virt_blocks+0x2b3/0xa10 fs/ocfs2/extent_map.c:976
       ocfs2_read_dir_block fs/ocfs2/dir.c:508 [inline]
       ocfs2_find_entry_el fs/ocfs2/dir.c:715 [inline]
       ocfs2_find_entry+0x437/0x26d0 fs/ocfs2/dir.c:1080
       ocfs2_find_files_on_disk+0xea/0x310 fs/ocfs2/dir.c:1982
       ocfs2_lookup_ino_from_name+0xad/0x1e0 fs/ocfs2/dir.c:2004
       _ocfs2_get_system_file_inode fs/ocfs2/sysfile.c:136 [inline]
       ocfs2_get_system_file_inode+0x314/0x7b0 fs/ocfs2/sysfile.c:112
       ocfs2_init_global_system_inodes+0x328/0x720 fs/ocfs2/super.c:458
       ocfs2_initialize_super fs/ocfs2/super.c:2276 [inline]
       ocfs2_fill_super+0x47b3/0x5890 fs/ocfs2/super.c:995
       mount_bdev+0x2c9/0x3f0 fs/super.c:1400
       legacy_get_tree+0xeb/0x180 fs/fs_context.c:611
       vfs_get_tree+0x88/0x270 fs/super.c:1530
       do_new_mount+0x2ba/0xb40 fs/namespace.c:3012
       do_mount fs/namespace.c:3355 [inline]
       __do_sys_mount fs/namespace.c:3563 [inline]
       __se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3540
       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

-> #1 (&osb->system_file_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
       ocfs2_get_system_file_inode+0x1a1/0x7b0 fs/ocfs2/sysfile.c:101
       ocfs2_reserve_suballoc_bits+0x16b/0x4c70 fs/ocfs2/suballoc.c:776
       ocfs2_reserve_new_metadata_blocks+0x418/0x9b0 fs/ocfs2/suballoc.c:978
       ocfs2_create_refcount_tree+0x32e/0x1530 fs/ocfs2/refcounttree.c:571
       ocfs2_reflink_remap_blocks+0x2f2/0x1f20 fs/ocfs2/refcounttree.c:4683
       ocfs2_remap_file_range+0x5f2/0x8d0 fs/ocfs2/file.c:2706
       do_clone_file_range+0x268/0x2d0 fs/remap_range.c:395
       vfs_clone_file_range+0x1fb/0x500 fs/remap_range.c:413
       ioctl_file_clone fs/ioctl.c:242 [inline]
       ioctl_file_clone_range fs/ioctl.c:262 [inline]
       do_vfs_ioctl+0x1b12/0x2b70 fs/ioctl.c:827
       __do_sys_ioctl fs/ioctl.c:872 [inline]
       __se_sys_ioctl+0x81/0x160 fs/ioctl.c:860
       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

-> #0 (&ocfs2_file_ip_alloc_sem_key/1){+.+.}-{3:3}:
       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
       down_write_nested+0x3b/0x60 kernel/locking/rwsem.c:1667
       ocfs2_remap_file_range+0x488/0x8d0 fs/ocfs2/file.c:2698
       do_clone_file_range+0x268/0x2d0 fs/remap_range.c:395
       vfs_clone_file_range+0x1fb/0x500 fs/remap_range.c:413
       ioctl_file_clone fs/ioctl.c:242 [inline]
       ioctl_file_clone_range fs/ioctl.c:262 [inline]
       do_vfs_ioctl+0x1b12/0x2b70 fs/ioctl.c:827
       __do_sys_ioctl fs/ioctl.c:872 [inline]
       __se_sys_ioctl+0x81/0x160 fs/ioctl.c:860
       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:
  &ocfs2_file_ip_alloc_sem_key/1 --> &osb->system_file_mutex --> &ocfs2_file_ip_alloc_sem_key

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&ocfs2_file_ip_alloc_sem_key);
                               lock(&osb->system_file_mutex);
                               lock(&ocfs2_file_ip_alloc_sem_key);
  lock(&ocfs2_file_ip_alloc_sem_key/1);

 *** DEADLOCK ***

4 locks held by syz-executor423/4312:
 #0: ffff88807e9d4460 (sb_writers#9){.+.+}-{0:0}, at: ioctl_file_clone fs/ioctl.c:242 [inline]
 #0: ffff88807e9d4460 (sb_writers#9){.+.+}-{0:0}, at: ioctl_file_clone_range fs/ioctl.c:262 [inline]
 #0: ffff88807e9d4460 (sb_writers#9){.+.+}-{0:0}, at: do_vfs_ioctl+0x1b12/0x2b70 fs/ioctl.c:827
 #1: ffff888070329808 (&sb->s_type->i_mutex_key#15){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
 #1: ffff888070329808 (&sb->s_type->i_mutex_key#15){+.+.}-{3:3}, at: lock_two_nondirectories+0xde/0x130 fs/inode.c:1122
 #2: ffff88807032a648 (&sb->s_type->i_mutex_key#15/4){+.+.}-{3:3}, at: ocfs2_reflink_inodes_lock+0x16e/0xdc0 fs/ocfs2/refcounttree.c:4751
 #3: ffff88807032a2e0 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_remap_file_range+0x45c/0x8d0 fs/ocfs2/file.c:2696

stack backtrace:
CPU: 0 PID: 4312 Comm: syz-executor423 Not tainted 5.15.176-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/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
 down_write_nested+0x3b/0x60 kernel/locking/rwsem.c:1667
 ocfs2_remap_file_range+0x488/0x8d0 fs/ocfs2/file.c:2698
 do_clone_file_range+0x268/0x2d0 fs/remap_range.c:395
 vfs_clone_file_range+0x1fb/0x500 fs/remap_range.c:413
 ioctl_file_clone fs/ioctl.c:242 [inline]
 ioctl_file_clone_range fs/ioctl.c:262 [inline]
 do_vfs_ioctl+0x1b12/0x2b70 fs/ioctl.c:827
 __do_sys_ioctl fs/ioctl.c:872 [inline]
 __se_sys_ioctl+0x81/0x160 fs/ioctl.c:860
 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:0x7fdb51ced329
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 18 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:00007ffd8426e208 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0031656c69662f2e RCX: 00007fdb51ced329
RDX: 0000000020000440 RSI: 000000004020940d RDI: 0000000000000005
RBP: 0000000000000000 R08: 00007ffd8426e240 R09: 00007ffd8426e240
R10: 00007ffd8426e240 R11: 0000000000000246 R12: 00007ffd8426e22c
R13: 0000000000000031 R14: 431bde82d7b634db R15: 00007ffd8426e260
 </TASK>

Crashes (32):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/01/17 07:23 linux-5.15.y 4735586da88e f9e07a6e .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2024/10/04 08:07 linux-5.15.y 3a5928702e71 d7906eff .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2025/04/03 11:16 linux-5.15.y 0c935c049b5c 996a9618 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2025/04/01 20:09 linux-5.15.y 0c935c049b5c b8645499 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2025/03/14 03:09 linux-5.15.y 0c935c049b5c e2826670 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2025/03/01 22:15 linux-5.15.y c16c81c81336 c3901742 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2025/03/01 22:15 linux-5.15.y c16c81c81336 c3901742 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2025/03/01 13:22 linux-5.15.y c16c81c81336 67cf5345 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2025/03/01 13:05 linux-5.15.y c16c81c81336 67cf5345 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2025/02/12 14:13 linux-5.15.y c16c81c81336 b27c2402 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2025/01/19 17:39 linux-5.15.y 4735586da88e f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2025/01/16 18:56 linux-5.15.y 4735586da88e f9e07a6e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2025/01/10 22:45 linux-5.15.y 4735586da88e 6dbc6a9b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2024/12/28 22:18 linux-5.15.y 91786f140358 d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2024/12/09 15:51 linux-5.15.y 0a51d2d4527b 9ac0fdc6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2024/12/09 15:44 linux-5.15.y 0a51d2d4527b 9ac0fdc6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2024/12/09 15:25 linux-5.15.y 0a51d2d4527b 9ac0fdc6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2024/12/09 15:16 linux-5.15.y 0a51d2d4527b 9ac0fdc6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2024/12/09 15:10 linux-5.15.y 0a51d2d4527b 9ac0fdc6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2024/12/09 15:07 linux-5.15.y 0a51d2d4527b 9ac0fdc6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2024/12/08 15:35 linux-5.15.y 0a51d2d4527b 9ac0fdc6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2024/11/22 00:06 linux-5.15.y 0a51d2d4527b 4b25d554 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2024/11/16 15:07 linux-5.15.y d98fd109f827 cfe3a04a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2024/10/15 14:20 linux-5.15.y 3a5928702e71 7eb57b4a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2024/10/12 03:19 linux-5.15.y 3a5928702e71 084d8178 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2024/10/12 03:19 linux-5.15.y 3a5928702e71 084d8178 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2024/10/03 12:40 linux-5.15.y 3a5928702e71 a4c7fd36 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan possible deadlock in ocfs2_remap_file_range
2025/04/27 21:24 linux-5.15.y f7347f400572 c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_remap_file_range
2025/03/29 20:07 linux-5.15.y 0c935c049b5c d3999433 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_remap_file_range
2025/03/24 02:35 linux-5.15.y 0c935c049b5c 875573af .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_remap_file_range
2024/11/26 15:45 linux-5.15.y 0a51d2d4527b e9a9a9f2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_remap_file_range
2024/11/26 15:39 linux-5.15.y 0a51d2d4527b e9a9a9f2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in ocfs2_remap_file_range
* Struck through repros no longer work on HEAD.