syzbot

JBD2: Ignoring recovery information on journal
ocfs2: Mounting device (7,0) on (node local, slot 0) with ordered data mode.
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.17/4451 is trying to acquire lock:
ffff888074b75488 (&osb->system_file_mutex){+.+.}-{3:3}, at: ocfs2_get_system_file_inode+0x1b6/0x7f0 fs/ocfs2/sysfile.c:101

but task is already holding lock:
ffff88805fac0660 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_expand_inline_dir fs/ocfs2/dir.c:2819 [inline]
ffff88805fac0660 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_extend_dir+0x691/0x4a20 fs/ocfs2/dir.c:3200

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}:
       down_read+0x44/0x2e0 kernel/locking/rwsem.c:1498
       ocfs2_read_virt_blocks+0x237/0x8d0 fs/ocfs2/extent_map.c:984
       ocfs2_read_dir_block fs/ocfs2/dir.c:508 [inline]
       ocfs2_find_entry_el fs/ocfs2/dir.c:715 [inline]
       ocfs2_find_entry+0x3ca/0x2060 fs/ocfs2/dir.c:1091
       ocfs2_find_files_on_disk+0xdb/0x2f0 fs/ocfs2/dir.c:1995
       ocfs2_lookup_ino_from_name+0x4f/0xf0 fs/ocfs2/dir.c:2017
       _ocfs2_get_system_file_inode fs/ocfs2/sysfile.c:136 [inline]
       ocfs2_get_system_file_inode+0x32b/0x7f0 fs/ocfs2/sysfile.c:112
       ocfs2_init_global_system_inodes+0x2f3/0x6d0 fs/ocfs2/super.c:458
       ocfs2_initialize_super fs/ocfs2/super.c:2279 [inline]
       ocfs2_fill_super+0x4060/0x50f0 fs/ocfs2/super.c:995
       mount_bdev+0x287/0x3c0 fs/super.c:1400
       legacy_get_tree+0xe6/0x180 fs/fs_context.c:611
       vfs_get_tree+0x88/0x270 fs/super.c:1530
       do_new_mount+0x24a/0xa40 fs/namespace.c:3034
       do_mount fs/namespace.c:3377 [inline]
       __do_sys_mount fs/namespace.c:3585 [inline]
       __se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3562
       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

-> #0 (&osb->system_file_mutex){+.+.}-{3:3}:
       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+0x2c42/0x7d10 kernel/locking/lockdep.c:5012
       lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
       __mutex_lock_common+0x1e3/0x2400 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+0x1b6/0x7f0 fs/ocfs2/sysfile.c:101
       ocfs2_reserve_suballoc_bits+0x12b/0x44d0 fs/ocfs2/suballoc.c:776
       ocfs2_reserve_new_metadata_blocks+0x412/0x9a0 fs/ocfs2/suballoc.c:978
       ocfs2_expand_inline_dir fs/ocfs2/dir.c:2838 [inline]
       ocfs2_extend_dir+0xcc9/0x4a20 fs/ocfs2/dir.c:3200
       ocfs2_prepare_dir_for_insert+0x2fc2/0x53c0 fs/ocfs2/dir.c:4321
       ocfs2_rename+0x1941/0x3960 fs/ocfs2/namei.c:1478
       vfs_rename+0xbe1/0x1100 fs/namei.c:4840
       do_renameat2+0x8b7/0xf60 fs/namei.c:4993
       __do_sys_rename fs/namei.c:5039 [inline]
       __se_sys_rename fs/namei.c:5037 [inline]
       __x64_sys_rename+0x82/0x90 fs/namei.c:5037
       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

other info that might help us debug this:

 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(&osb->system_file_mutex);

 *** DEADLOCK ***

4 locks held by syz.0.17/4451:
 #0: ffff88807b746460 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:386
 #1: ffff88805fac09c8 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: lock_rename include/linux/fs.h:-1 [inline]
 #1: ffff88805fac09c8 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: do_renameat2+0x43d/0xf60 fs/namei.c:4932
 #2: ffff88805fbd09c8 (&sb->s_type->i_mutex_key#21/4){+.+.}-{3:3}, at: vfs_rename+0x7e3/0x1100 fs/namei.c:4811
 #3: ffff88805fac0660 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_expand_inline_dir fs/ocfs2/dir.c:2819 [inline]
 #3: ffff88805fac0660 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_extend_dir+0x691/0x4a20 fs/ocfs2/dir.c:3200

stack backtrace:
CPU: 1 PID: 4451 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
 check_noncircular+0x296/0x330 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+0x2c42/0x7d10 kernel/locking/lockdep.c:5012
 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623
 __mutex_lock_common+0x1e3/0x2400 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+0x1b6/0x7f0 fs/ocfs2/sysfile.c:101
 ocfs2_reserve_suballoc_bits+0x12b/0x44d0 fs/ocfs2/suballoc.c:776
 ocfs2_reserve_new_metadata_blocks+0x412/0x9a0 fs/ocfs2/suballoc.c:978
 ocfs2_expand_inline_dir fs/ocfs2/dir.c:2838 [inline]
 ocfs2_extend_dir+0xcc9/0x4a20 fs/ocfs2/dir.c:3200
 ocfs2_prepare_dir_for_insert+0x2fc2/0x53c0 fs/ocfs2/dir.c:4321
 ocfs2_rename+0x1941/0x3960 fs/ocfs2/namei.c:1478
 vfs_rename+0xbe1/0x1100 fs/namei.c:4840
 do_renameat2+0x8b7/0xf60 fs/namei.c:4993
 __do_sys_rename fs/namei.c:5039 [inline]
 __se_sys_rename fs/namei.c:5037 [inline]
 __x64_sys_rename+0x82/0x90 fs/namei.c:5037
 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
RIP: 0033:0x7f970834deb9
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffc4d8b0448 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007f97085c8fa0 RCX: 00007f970834deb9
RDX: 0000000000000000 RSI: 0000200000001900 RDI: 0000200000000140
RBP: 00007f97083bbc1f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f97085c8fac R14: 00007f97085c8fa0 R15: 00007f97085c8fa0
 </TASK>
syz.0.17 (4451) used greatest stack depth: 18192 bytes left