====================================================== WARNING: possible circular locking dependency detected 5.15.161-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor/3959 is trying to acquire lock: ffff0000d40343f8 (&journal->j_checkpoint_mutex){+.+.}-{3:3}, at: __jbd2_log_wait_for_space+0x1a4/0x5cc fs/jbd2/checkpoint.c:71 but task is already holding lock: ffff0000d402e558 (sb_pagefaults){.+.+}-{0:0}, at: __sb_start_write include/linux/fs.h:1811 [inline] ffff0000d402e558 (sb_pagefaults){.+.+}-{0:0}, at: sb_start_pagefault include/linux/fs.h:1910 [inline] ffff0000d402e558 (sb_pagefaults){.+.+}-{0:0}, at: ext4_page_mkwrite+0x170/0x10c4 fs/ext4/inode.c:6110 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (sb_pagefaults){.+.+}-{0:0}: percpu_down_read+0xec/0x3a8 include/linux/percpu-rwsem.h:51 __sb_start_write include/linux/fs.h:1811 [inline] sb_start_pagefault include/linux/fs.h:1910 [inline] ext4_page_mkwrite+0x170/0x10c4 fs/ext4/inode.c:6110 do_page_mkwrite+0x144/0x37c mm/memory.c:2892 wp_page_shared+0x14c/0x398 mm/memory.c:3229 do_wp_page+0x7cc/0x9c4 mm/memory.c:3330 handle_pte_fault mm/memory.c:4639 [inline] __handle_mm_fault mm/memory.c:4756 [inline] handle_mm_fault+0x1bf8/0x3424 mm/memory.c:4854 __do_page_fault arch/arm64/mm/fault.c:505 [inline] do_page_fault+0x700/0xb60 arch/arm64/mm/fault.c:605 do_mem_abort+0x70/0x1d8 arch/arm64/mm/fault.c:819 el0_da+0x94/0x20c arch/arm64/kernel/entry-common.c:494 el0t_64_sync_handler+0xc0/0xe4 arch/arm64/kernel/entry-common.c:629 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584 -> #2 (&mm->mmap_lock){++++}-{3:3}: __might_fault+0xc8/0x128 mm/memory.c:5328 fault_in_readable+0xdc/0x56c mm/gup.c:1793 fault_in_iov_iter_readable+0x130/0x1b0 lib/iov_iter.c:460 generic_perform_write+0x198/0x520 mm/filemap.c:3775 ext4_buffered_write_iter+0x3fc/0x528 fs/ext4/file.c:268 ext4_file_write_iter+0x688/0x162c call_write_iter include/linux/fs.h:2172 [inline] new_sync_write fs/read_write.c:507 [inline] vfs_write+0x87c/0xb3c fs/read_write.c:594 ksys_write+0x15c/0x26c fs/read_write.c:647 __do_sys_write fs/read_write.c:659 [inline] __se_sys_write fs/read_write.c:656 [inline] __arm64_sys_write+0x7c/0x90 fs/read_write.c:656 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181 el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608 el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584 -> #1 (&sb->s_type->i_mutex_key#9){++++}-{3:3}: down_read+0xc0/0x398 kernel/locking/rwsem.c:1498 inode_lock_shared include/linux/fs.h:799 [inline] ext4_bmap+0x58/0x36c fs/ext4/inode.c:3152 bmap+0xa8/0xe8 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+0x63c/0xaa0 fs/jbd2/journal.c:2496 ext4_ioctl_checkpoint fs/ext4/ioctl.c:849 [inline] __ext4_ioctl fs/ext4/ioctl.c:1267 [inline] ext4_ioctl+0x3454/0x61bc fs/ext4/ioctl.c:1276 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:874 [inline] __se_sys_ioctl fs/ioctl.c:860 [inline] __arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:860 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181 el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608 el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584 -> #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 kernel/locking/lockdep.c:3788 [inline] __lock_acquire+0x32d4/0x7638 kernel/locking/lockdep.c:5012 lock_acquire+0x240/0x77c kernel/locking/lockdep.c:5623 __mutex_lock_common+0x194/0x2154 kernel/locking/mutex.c:596 mutex_lock_io_nested+0xcc/0x12c kernel/locking/mutex.c:777 __jbd2_log_wait_for_space+0x1a4/0x5cc fs/jbd2/checkpoint.c:71 add_transaction_credits+0x814/0xb90 fs/jbd2/transaction.c:299 start_this_handle+0x578/0x12a4 fs/jbd2/transaction.c:423 jbd2__journal_start+0x29c/0x7b4 fs/jbd2/transaction.c:521 __ext4_journal_start_sb+0x358/0x70c fs/ext4/ext4_jbd2.c:105 __ext4_journal_start fs/ext4/ext4_jbd2.h:326 [inline] ext4_dirty_inode+0x9c/0x100 fs/ext4/inode.c:5990 __mark_inode_dirty+0x2b0/0x10f4 fs/fs-writeback.c:2464 generic_update_time+0x218/0x23c fs/inode.c:1817 inode_update_time fs/inode.c:1830 [inline] file_update_time+0x378/0x3f0 fs/inode.c:2019 ext4_page_mkwrite+0x188/0x10c4 fs/ext4/inode.c:6111 do_page_mkwrite+0x144/0x37c mm/memory.c:2892 wp_page_shared+0x14c/0x398 mm/memory.c:3229 do_wp_page+0x7cc/0x9c4 mm/memory.c:3330 handle_pte_fault mm/memory.c:4639 [inline] __handle_mm_fault mm/memory.c:4756 [inline] handle_mm_fault+0x1bf8/0x3424 mm/memory.c:4854 __do_page_fault arch/arm64/mm/fault.c:505 [inline] do_page_fault+0x700/0xb60 arch/arm64/mm/fault.c:605 do_mem_abort+0x70/0x1d8 arch/arm64/mm/fault.c:819 el0_da+0x94/0x20c arch/arm64/kernel/entry-common.c:494 el0t_64_sync_handler+0xc0/0xe4 arch/arm64/kernel/entry-common.c:629 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584 other info that might help us debug this: Chain exists of: &journal->j_checkpoint_mutex --> &mm->mmap_lock --> sb_pagefaults Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(sb_pagefaults); lock(&mm->mmap_lock); lock(sb_pagefaults); lock(&journal->j_checkpoint_mutex); *** DEADLOCK *** 2 locks held by syz-executor/3959: #0: ffff0000c193d758 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_trylock include/linux/mmap_lock.h:136 [inline] #0: ffff0000c193d758 (&mm->mmap_lock){++++}-{3:3}, at: do_page_fault+0x380/0xb60 arch/arm64/mm/fault.c:586 #1: ffff0000d402e558 (sb_pagefaults){.+.+}-{0:0}, at: __sb_start_write include/linux/fs.h:1811 [inline] #1: ffff0000d402e558 (sb_pagefaults){.+.+}-{0:0}, at: sb_start_pagefault include/linux/fs.h:1910 [inline] #1: ffff0000d402e558 (sb_pagefaults){.+.+}-{0:0}, at: ext4_page_mkwrite+0x170/0x10c4 fs/ext4/inode.c:6110 stack backtrace: CPU: 0 PID: 3959 Comm: syz-executor Not tainted 5.15.161-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024 Call trace: dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216 __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106 dump_stack+0x1c/0x58 lib/dump_stack.c:113 print_circular_bug+0x150/0x1b8 kernel/locking/lockdep.c:2011 check_noncircular+0x2cc/0x378 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+0x32d4/0x7638 kernel/locking/lockdep.c:5012 lock_acquire+0x240/0x77c kernel/locking/lockdep.c:5623 __mutex_lock_common+0x194/0x2154 kernel/locking/mutex.c:596 mutex_lock_io_nested+0xcc/0x12c kernel/locking/mutex.c:777 __jbd2_log_wait_for_space+0x1a4/0x5cc fs/jbd2/checkpoint.c:71 add_transaction_credits+0x814/0xb90 fs/jbd2/transaction.c:299 start_this_handle+0x578/0x12a4 fs/jbd2/transaction.c:423 jbd2__journal_start+0x29c/0x7b4 fs/jbd2/transaction.c:521 __ext4_journal_start_sb+0x358/0x70c fs/ext4/ext4_jbd2.c:105 __ext4_journal_start fs/ext4/ext4_jbd2.h:326 [inline] ext4_dirty_inode+0x9c/0x100 fs/ext4/inode.c:5990 __mark_inode_dirty+0x2b0/0x10f4 fs/fs-writeback.c:2464 generic_update_time+0x218/0x23c fs/inode.c:1817 inode_update_time fs/inode.c:1830 [inline] file_update_time+0x378/0x3f0 fs/inode.c:2019 ext4_page_mkwrite+0x188/0x10c4 fs/ext4/inode.c:6111 do_page_mkwrite+0x144/0x37c mm/memory.c:2892 wp_page_shared+0x14c/0x398 mm/memory.c:3229 do_wp_page+0x7cc/0x9c4 mm/memory.c:3330 handle_pte_fault mm/memory.c:4639 [inline] __handle_mm_fault mm/memory.c:4756 [inline] handle_mm_fault+0x1bf8/0x3424 mm/memory.c:4854 __do_page_fault arch/arm64/mm/fault.c:505 [inline] do_page_fault+0x700/0xb60 arch/arm64/mm/fault.c:605 do_mem_abort+0x70/0x1d8 arch/arm64/mm/fault.c:819 el0_da+0x94/0x20c arch/arm64/kernel/entry-common.c:494 el0t_64_sync_handler+0xc0/0xe4 arch/arm64/kernel/entry-common.c:629 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584