REISERFS (device loop2): checking transaction log (loop2) REISERFS (device loop2): Using tea hash to sort names ====================================================== WARNING: possible circular locking dependency detected 6.1.34-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.2/7382 is trying to acquire lock: ffff0000c8916d48 (&mm->mmap_lock){++++}-{3:3}, at: __might_fault+0x9c/0x124 mm/memory.c:5654 but task is already holding lock: ffff0000ddaee090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x7c/0xe8 fs/reiserfs/lock.c:27 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&sbi->lock){+.+.}-{3:3}: __mutex_lock_common+0x190/0x21a0 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799 reiserfs_write_lock+0x7c/0xe8 fs/reiserfs/lock.c:27 reiserfs_dirty_inode+0xe4/0x204 fs/reiserfs/super.c:704 __mark_inode_dirty+0x2f8/0x1354 fs/fs-writeback.c:2411 generic_update_time fs/inode.c:1859 [inline] inode_update_time fs/inode.c:1872 [inline] __file_update_time+0x1f4/0x21c fs/inode.c:2060 file_update_time+0x2cc/0x348 fs/inode.c:2091 filemap_page_mkwrite+0x310/0x938 mm/filemap.c:3422 do_page_mkwrite+0x144/0x37c mm/memory.c:2973 do_shared_fault mm/memory.c:4628 [inline] do_fault mm/memory.c:4696 [inline] handle_pte_fault mm/memory.c:4964 [inline] __handle_mm_fault mm/memory.c:5106 [inline] handle_mm_fault+0x195c/0x3e9c mm/memory.c:5227 __do_page_fault arch/arm64/mm/fault.c:512 [inline] do_page_fault+0x634/0xac4 arch/arm64/mm/fault.c:612 do_translation_fault+0x94/0xc8 arch/arm64/mm/fault.c:695 do_mem_abort+0x74/0x200 arch/arm64/mm/fault.c:831 el0_da+0x70/0x184 arch/arm64/kernel/entry-common.c:515 el0t_64_sync_handler+0xcc/0xf0 arch/arm64/kernel/entry-common.c:658 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581 -> #1 (sb_pagefaults){.+.+}-{0:0}: percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1832 [inline] sb_start_pagefault include/linux/fs.h:1936 [inline] filemap_page_mkwrite+0x164/0x938 mm/filemap.c:3421 do_page_mkwrite+0x144/0x37c mm/memory.c:2973 do_shared_fault mm/memory.c:4628 [inline] do_fault mm/memory.c:4696 [inline] handle_pte_fault mm/memory.c:4964 [inline] __handle_mm_fault mm/memory.c:5106 [inline] handle_mm_fault+0x195c/0x3e9c mm/memory.c:5227 __do_page_fault arch/arm64/mm/fault.c:512 [inline] do_page_fault+0x634/0xac4 arch/arm64/mm/fault.c:612 do_translation_fault+0x94/0xc8 arch/arm64/mm/fault.c:695 do_mem_abort+0x74/0x200 arch/arm64/mm/fault.c:831 el0_da+0x70/0x184 arch/arm64/kernel/entry-common.c:515 el0t_64_sync_handler+0xcc/0xf0 arch/arm64/kernel/entry-common.c:658 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581 -> #0 (&mm->mmap_lock){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3098 [inline] check_prevs_add kernel/locking/lockdep.c:3217 [inline] validate_chain kernel/locking/lockdep.c:3832 [inline] __lock_acquire+0x3338/0x764c kernel/locking/lockdep.c:5056 lock_acquire+0x26c/0x7cc kernel/locking/lockdep.c:5669 __might_fault+0xc4/0x124 mm/memory.c:5655 reiserfs_ioctl+0x10c/0x454 fs/reiserfs/ioctl.c:96 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl fs/ioctl.c:856 [inline] __arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:856 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581 other info that might help us debug this: Chain exists of: &mm->mmap_lock --> sb_pagefaults --> &sbi->lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sbi->lock); lock(sb_pagefaults); lock(&sbi->lock); lock(&mm->mmap_lock); *** DEADLOCK *** 1 lock held by syz-executor.2/7382: #0: ffff0000ddaee090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x7c/0xe8 fs/reiserfs/lock.c:27 stack backtrace: CPU: 0 PID: 7382 Comm: syz-executor.2 Not tainted 6.1.34-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023 Call trace: dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165 __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:2056 check_noncircular+0x2cc/0x378 kernel/locking/lockdep.c:2178 check_prev_add kernel/locking/lockdep.c:3098 [inline] check_prevs_add kernel/locking/lockdep.c:3217 [inline] validate_chain kernel/locking/lockdep.c:3832 [inline] __lock_acquire+0x3338/0x764c kernel/locking/lockdep.c:5056 lock_acquire+0x26c/0x7cc kernel/locking/lockdep.c:5669 __might_fault+0xc4/0x124 mm/memory.c:5655 reiserfs_ioctl+0x10c/0x454 fs/reiserfs/ioctl.c:96 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl fs/ioctl.c:856 [inline] __arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:856 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581