====================================================== WARNING: possible circular locking dependency detected 6.13.0-rc2-syzkaller-gfac04efc5c79 #0 Not tainted ------------------------------------------------------ syz.5.490/8376 is trying to acquire lock: ffff0000f3e06178 (&sb->s_type->i_mutex_key#35){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:818 [inline] ffff0000f3e06178 (&sb->s_type->i_mutex_key#35){+.+.}-{4:4}, at: hfsplus_file_fsync+0xd8/0x4c8 fs/hfsplus/inode.c:311 but task is already holding lock: ffff0000ca489de8 (&q->q_usage_counter(io)#17){++++}-{0:0}, at: loop_set_status+0x1ac/0x7f4 drivers/block/loop.c:1267 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&q->q_usage_counter(io)#17){++++}-{0:0}: bio_queue_enter block/blk.h:75 [inline] blk_mq_submit_bio+0x1254/0x2070 block/blk-mq.c:3092 __submit_bio+0x1a0/0x4f8 block/blk-core.c:629 __submit_bio_noacct_mq block/blk-core.c:710 [inline] submit_bio_noacct_nocheck+0x3bc/0xcbc block/blk-core.c:739 submit_bio_noacct+0xc6c/0x166c block/blk-core.c:868 submit_bio+0x374/0x564 block/blk-core.c:910 mpage_bio_submit_write fs/mpage.c:83 [inline] mpage_writepages+0x150/0x1b8 fs/mpage.c:668 hfsplus_writepages+0x30/0x40 fs/hfsplus/inode.c:149 do_writepages+0x304/0x7d0 mm/page-writeback.c:2702 filemap_fdatawrite_wbc mm/filemap.c:397 [inline] __filemap_fdatawrite_range mm/filemap.c:430 [inline] filemap_write_and_wait_range+0x200/0x314 mm/filemap.c:684 filemap_write_and_wait include/linux/pagemap.h:68 [inline] hfsplus_file_fsync+0x184/0x4c8 fs/hfsplus/inode.c:322 vfs_fsync_range+0x160/0x19c fs/sync.c:187 generic_write_sync include/linux/fs.h:2904 [inline] generic_file_write_iter+0x228/0x2b4 mm/filemap.c:4186 new_sync_write fs/read_write.c:586 [inline] vfs_write+0x920/0xcf4 fs/read_write.c:679 ksys_write+0x15c/0x26c fs/read_write.c:731 __do_sys_write fs/read_write.c:742 [inline] __se_sys_write fs/read_write.c:739 [inline] __arm64_sys_write+0x7c/0x90 fs/read_write.c:739 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600 -> #0 (&sb->s_type->i_mutex_key#35){+.+.}-{4:4}: check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain kernel/locking/lockdep.c:3904 [inline] __lock_acquire+0x34f0/0x7904 kernel/locking/lockdep.c:5226 lock_acquire+0x23c/0x724 kernel/locking/lockdep.c:5849 down_write+0x50/0xc0 kernel/locking/rwsem.c:1577 inode_lock include/linux/fs.h:818 [inline] hfsplus_file_fsync+0xd8/0x4c8 fs/hfsplus/inode.c:311 vfs_fsync_range fs/sync.c:187 [inline] vfs_fsync+0x154/0x18c fs/sync.c:201 __loop_update_dio+0x248/0x420 drivers/block/loop.c:204 loop_set_status+0x538/0x7f4 drivers/block/loop.c:1289 lo_ioctl+0xf10/0x1c48 blkdev_ioctl+0x3a8/0xa8c block/ioctl.c:693 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:906 [inline] __se_sys_ioctl fs/ioctl.c:892 [inline] __arm64_sys_ioctl+0x14c/0x1cc fs/ioctl.c:892 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&q->q_usage_counter(io)#17); lock(&sb->s_type->i_mutex_key#35); lock(&q->q_usage_counter(io)#17); lock(&sb->s_type->i_mutex_key#35); *** DEADLOCK *** 3 locks held by syz.5.490/8376: #0: ffff0000c9de6360 (&lo->lo_mutex){+.+.}-{4:4}, at: loop_set_status+0x40/0x7f4 drivers/block/loop.c:1251 #1: ffff0000ca489de8 (&q->q_usage_counter(io)#17){++++}-{0:0}, at: loop_set_status+0x1ac/0x7f4 drivers/block/loop.c:1267 #2: ffff0000ca489e20 (&q->q_usage_counter(queue)){+.+.}-{0:0}, at: loop_set_status+0x1ac/0x7f4 drivers/block/loop.c:1267 stack backtrace: CPU: 1 UID: 0 PID: 8376 Comm: syz.5.490 Not tainted 6.13.0-rc2-syzkaller-gfac04efc5c79 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Call trace: show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:484 (C) __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:120 dump_stack+0x1c/0x28 lib/dump_stack.c:129 print_circular_bug+0x154/0x1c0 kernel/locking/lockdep.c:2074 check_noncircular+0x310/0x404 kernel/locking/lockdep.c:2206 check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain kernel/locking/lockdep.c:3904 [inline] __lock_acquire+0x34f0/0x7904 kernel/locking/lockdep.c:5226 lock_acquire+0x23c/0x724 kernel/locking/lockdep.c:5849 down_write+0x50/0xc0 kernel/locking/rwsem.c:1577 inode_lock include/linux/fs.h:818 [inline] hfsplus_file_fsync+0xd8/0x4c8 fs/hfsplus/inode.c:311 vfs_fsync_range fs/sync.c:187 [inline] vfs_fsync+0x154/0x18c fs/sync.c:201 __loop_update_dio+0x248/0x420 drivers/block/loop.c:204 loop_set_status+0x538/0x7f4 drivers/block/loop.c:1289 lo_ioctl+0xf10/0x1c48 blkdev_ioctl+0x3a8/0xa8c block/ioctl.c:693 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:906 [inline] __se_sys_ioctl fs/ioctl.c:892 [inline] __arm64_sys_ioctl+0x14c/0x1cc fs/ioctl.c:892 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600