syzbot

loop0: detected capacity change from 0 to 32768
JBD2: Ignoring recovery information on journal
ocfs2: Mounting device (7,0) on (node local, slot 0) with writeback data mode.
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.0.49/4414 is trying to acquire lock:
ffff88807949d488 (&osb->system_file_mutex){+.+.}-{3:3}, at: ocfs2_get_system_file_inode+0x1b5/0x760 fs/ocfs2/sysfile.c:101

but task is already holding lock:
ffff88805c7394a0 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_write_begin+0x18a/0x300 fs/ocfs2/aops.c:1903

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+0x23f/0x8a0 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+0x3d1/0x1f90 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+0x319/0x760 fs/ocfs2/sysfile.c:112
       ocfs2_init_global_system_inodes+0x316/0x650 fs/ocfs2/super.c:458
       ocfs2_initialize_super fs/ocfs2/super.c:2279 [inline]
       ocfs2_fill_super+0x3dbf/0x4d80 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+0x2d6/0x3c0 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+0x2c33/0x7c60 kernel/locking/lockdep.c:5012
       lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
       __mutex_lock_common+0x1eb/0x2390 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+0x1b5/0x760 fs/ocfs2/sysfile.c:101
       ocfs2_reserve_suballoc_bits+0x139/0x4350 fs/ocfs2/suballoc.c:776
       ocfs2_reserve_cluster_bitmap_bits fs/ocfs2/suballoc.c:1128 [inline]
       ocfs2_reserve_clusters_with_limit+0x2f8/0xba0 fs/ocfs2/suballoc.c:1173
       ocfs2_reserve_clusters fs/ocfs2/suballoc.c:1223 [inline]
       ocfs2_lock_allocators+0x2f7/0x5b0 fs/ocfs2/suballoc.c:2669
       ocfs2_write_begin_nolock+0x2216/0x4180 fs/ocfs2/aops.c:1741
       ocfs2_write_begin+0x1ab/0x300 fs/ocfs2/aops.c:1905
       generic_perform_write+0x2aa/0x530 mm/filemap.c:3785
       __generic_file_write_iter+0x25f/0x4e0 mm/filemap.c:3912
       ocfs2_file_write_iter+0x1578/0x1cf0 fs/ocfs2/file.c:2472
       call_write_iter include/linux/fs.h:2173 [inline]
       aio_write+0x513/0x720 fs/aio.c:1594
       __io_submit_one fs/aio.c:-1 [inline]
       io_submit_one+0x6ac/0x1330 fs/aio.c:2013
       __do_sys_io_submit fs/aio.c:2072 [inline]
       __se_sys_io_submit+0x190/0x300 fs/aio.c:2042
       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 ***

2 locks held by syz.0.49/4414:
 #0: ffff88805c739808 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
 #0: ffff88805c739808 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: ocfs2_file_write_iter+0x401/0x1cf0 fs/ocfs2/file.c:2402
 #1: ffff88805c7394a0 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_write_begin+0x18a/0x300 fs/ocfs2/aops.c:1903

stack backtrace:
CPU: 1 PID: 4414 Comm: syz.0.49 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
 check_noncircular+0x274/0x310 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+0x2c33/0x7c60 kernel/locking/lockdep.c:5012
 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
 __mutex_lock_common+0x1eb/0x2390 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+0x1b5/0x760 fs/ocfs2/sysfile.c:101
 ocfs2_reserve_suballoc_bits+0x139/0x4350 fs/ocfs2/suballoc.c:776
 ocfs2_reserve_cluster_bitmap_bits fs/ocfs2/suballoc.c:1128 [inline]
 ocfs2_reserve_clusters_with_limit+0x2f8/0xba0 fs/ocfs2/suballoc.c:1173
 ocfs2_reserve_clusters fs/ocfs2/suballoc.c:1223 [inline]
 ocfs2_lock_allocators+0x2f7/0x5b0 fs/ocfs2/suballoc.c:2669
 ocfs2_write_begin_nolock+0x2216/0x4180 fs/ocfs2/aops.c:1741
 ocfs2_write_begin+0x1ab/0x300 fs/ocfs2/aops.c:1905
 generic_perform_write+0x2aa/0x530 mm/filemap.c:3785
 __generic_file_write_iter+0x25f/0x4e0 mm/filemap.c:3912
 ocfs2_file_write_iter+0x1578/0x1cf0 fs/ocfs2/file.c:2472
 call_write_iter include/linux/fs.h:2173 [inline]
 aio_write+0x513/0x720 fs/aio.c:1594
 __io_submit_one fs/aio.c:-1 [inline]
 io_submit_one+0x6ac/0x1330 fs/aio.c:2013
 __do_sys_io_submit fs/aio.c:2072 [inline]
 __se_sys_io_submit+0x190/0x300 fs/aio.c:2042
 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:0x7fb214f85749
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffcfaff2fb8 EFLAGS: 00000246 ORIG_RAX: 00000000000000d1
RAX: ffffffffffffffda RBX: 00007fb2151dbfa0 RCX: 00007fb214f85749
RDX: 0000200000000540 RSI: 000000000000003b RDI: 00007fb2151b5000
RBP: 00007fb215009f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fb2151dbfa0 R14: 00007fb2151dbfa0 R15: 0000000000000003
 </TASK>
OCFS2: ERROR (device loop0): int ocfs2_claim_suballoc_bits(struct ocfs2_alloc_context *, handle_t *, u32, u32, struct ocfs2_suballoc_result *): Chain allocator dinode 23 has 4294967295 used bits but only 16777215 total
On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted.
OCFS2: File system is now read-only.
(syz.0.49,4414,1):ocfs2_claim_suballoc_bits:1983 ERROR: status = -30
(syz.0.49,4414,1):__ocfs2_claim_clusters:2355 ERROR: status = -30
(syz.0.49,4414,1):__ocfs2_claim_clusters:2363 ERROR: status = -30
(syz.0.49,4414,1):ocfs2_add_clusters_in_btree:4831 ERROR: status = -30
(syz.0.49,4414,1):ocfs2_write_cluster:1154 ERROR: status = -30
(syz.0.49,4414,1):ocfs2_write_cluster_by_desc:1249 ERROR: status = -30
(syz.0.49,4414,1):ocfs2_write_begin_nolock:1821 ERROR: status = -30
(syz.0.49,4414,1):ocfs2_write_begin:1908 ERROR: status = -30