====================================================== WARNING: possible circular locking dependency detected 5.15.152-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.3/32024 is trying to acquire lock: ffff88814ad1a3f8 (&journal->j_checkpoint_mutex){+.+.}-{3:3}, at: __jbd2_log_wait_for_space+0x213/0x760 fs/jbd2/checkpoint.c:71 but task is already holding lock: ffff88802f63f198 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline] ffff88802f63f198 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: ext4_buffered_write_iter+0xa0/0x360 fs/ext4/file.c:262 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&sb->s_type->i_mutex_key#9){++++}-{3:3}: lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623 down_read+0x45/0x2e0 kernel/locking/rwsem.c:1488 inode_lock_shared include/linux/fs.h:799 [inline] ext4_bmap+0x4b/0x410 fs/ext4/inode.c:3152 bmap+0xa1/0xd0 fs/inode.c:1756 jbd2_journal_bmap fs/jbd2/journal.c:980 [inline] __jbd2_journal_erase fs/jbd2/journal.c:1790 [inline] jbd2_journal_flush+0x7a2/0xc90 fs/jbd2/journal.c:2496 ext4_ioctl_checkpoint fs/ext4/ioctl.c:849 [inline] __ext4_ioctl fs/ext4/ioctl.c:1267 [inline] ext4_ioctl+0x3249/0x5b80 fs/ext4/ioctl.c:1276 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:874 [inline] __se_sys_ioctl+0xf1/0x160 fs/ioctl.c:860 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x61/0xcb -> #0 (&journal->j_checkpoint_mutex){+.+.}-{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 __mutex_lock_common+0x1da/0x25a0 kernel/locking/mutex.c:596 mutex_lock_io_nested+0x45/0x60 kernel/locking/mutex.c:777 __jbd2_log_wait_for_space+0x213/0x760 fs/jbd2/checkpoint.c:71 add_transaction_credits+0x950/0xc00 fs/jbd2/transaction.c:299 start_this_handle+0x747/0x1570 fs/jbd2/transaction.c:423 jbd2__journal_start+0x2d1/0x5c0 fs/jbd2/transaction.c:521 __ext4_journal_start_sb+0x175/0x370 fs/ext4/ext4_jbd2.c:105 __ext4_journal_start fs/ext4/ext4_jbd2.h:326 [inline] ext4_dirty_inode+0x8b/0x100 fs/ext4/inode.c:5990 __mark_inode_dirty+0x2fd/0xd60 fs/fs-writeback.c:2464 mark_inode_dirty include/linux/fs.h:2438 [inline] generic_write_end+0x232/0x440 fs/buffer.c:2204 ext4_da_write_end+0x72d/0x9e0 fs/ext4/inode.c:3084 generic_perform_write+0x3b7/0x5b0 mm/filemap.c:3796 ext4_buffered_write_iter+0x227/0x360 fs/ext4/file.c:268 ext4_file_write_iter+0x87c/0x1990 __kernel_write+0x5b1/0xa60 fs/read_write.c:539 __dump_emit+0x264/0x3a0 fs/coredump.c:875 dump_user_range+0x91/0x320 fs/coredump.c:949 elf_core_dump+0x3c7d/0x4570 fs/binfmt_elf.c:2285 do_coredump+0x1852/0x31e0 fs/coredump.c:826 get_signal+0xc06/0x14e0 kernel/signal.c:2875 arch_do_signal_or_restart+0xc3/0x1890 arch/x86/kernel/signal.c:867 handle_signal_work kernel/entry/common.c:148 [inline] exit_to_user_mode_loop+0x97/0x130 kernel/entry/common.c:172 exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:208 irqentry_exit_to_user_mode+0x5/0x40 kernel/entry/common.c:314 exc_page_fault+0x342/0x740 arch/x86/mm/fault.c:1544 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:568 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sb->s_type->i_mutex_key#9); lock(&journal->j_checkpoint_mutex); lock(&sb->s_type->i_mutex_key#9); lock(&journal->j_checkpoint_mutex); *** DEADLOCK *** 2 locks held by syz-executor.3/32024: #0: ffff88814acd6460 (sb_writers#5){.+.+}-{0:0}, at: do_coredump+0x1825/0x31e0 fs/coredump.c:825 #1: ffff88802f63f198 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline] #1: ffff88802f63f198 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: ext4_buffered_write_iter+0xa0/0x360 fs/ext4/file.c:262 stack backtrace: CPU: 1 PID: 32024 Comm: syz-executor.3 Not tainted 5.15.152-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e3/0x2cb 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 __mutex_lock_common+0x1da/0x25a0 kernel/locking/mutex.c:596 mutex_lock_io_nested+0x45/0x60 kernel/locking/mutex.c:777 __jbd2_log_wait_for_space+0x213/0x760 fs/jbd2/checkpoint.c:71 add_transaction_credits+0x950/0xc00 fs/jbd2/transaction.c:299 start_this_handle+0x747/0x1570 fs/jbd2/transaction.c:423 jbd2__journal_start+0x2d1/0x5c0 fs/jbd2/transaction.c:521 __ext4_journal_start_sb+0x175/0x370 fs/ext4/ext4_jbd2.c:105 __ext4_journal_start fs/ext4/ext4_jbd2.h:326 [inline] ext4_dirty_inode+0x8b/0x100 fs/ext4/inode.c:5990 __mark_inode_dirty+0x2fd/0xd60 fs/fs-writeback.c:2464 mark_inode_dirty include/linux/fs.h:2438 [inline] generic_write_end+0x232/0x440 fs/buffer.c:2204 ext4_da_write_end+0x72d/0x9e0 fs/ext4/inode.c:3084 generic_perform_write+0x3b7/0x5b0 mm/filemap.c:3796 ext4_buffered_write_iter+0x227/0x360 fs/ext4/file.c:268 ext4_file_write_iter+0x87c/0x1990 __kernel_write+0x5b1/0xa60 fs/read_write.c:539 __dump_emit+0x264/0x3a0 fs/coredump.c:875 dump_user_range+0x91/0x320 fs/coredump.c:949 elf_core_dump+0x3c7d/0x4570 fs/binfmt_elf.c:2285 do_coredump+0x1852/0x31e0 fs/coredump.c:826 get_signal+0xc06/0x14e0 kernel/signal.c:2875 arch_do_signal_or_restart+0xc3/0x1890 arch/x86/kernel/signal.c:867 handle_signal_work kernel/entry/common.c:148 [inline] exit_to_user_mode_loop+0x97/0x130 kernel/entry/common.c:172 exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:208 irqentry_exit_to_user_mode+0x5/0x40 kernel/entry/common.c:314 exc_page_fault+0x342/0x740 arch/x86/mm/fault.c:1544 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:568 RIP: 0033:0xf25b51 Code: Unable to access opcode bytes at RIP 0xf25b27. RSP: 002b:00000000200000c8 EFLAGS: 00010217 RAX: 0000000000000000 RBX: 00007f135b00af80 RCX: 00007f135aedcda9 RDX: 0000000020000140 RSI: 00000000200000c0 RDI: 0000000030980000 RBP: 00007f135af2947a R08: 0000000020000240 R09: 0000000020000240 R10: 0000000020000200 R11: 0000000000000206 R12: 0000000000000000 R13: 000000000000000b R14: 00007f135b00af80 R15: 00007fffd0111298