====================================================== WARNING: possible circular locking dependency detected 6.1.63-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.2/12858 is trying to acquire lock: ffff88809b697090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x76/0xd0 fs/reiserfs/lock.c:27 but task is already holding lock: ffff88801b7e4558 (sb_pagefaults#5){.+.+}-{0:0}, at: do_page_mkwrite+0x1a1/0x5f0 mm/memory.c:2992 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (sb_pagefaults#5){.+.+}-{0:0}: lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5661 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+0x16a/0x630 mm/filemap.c:3475 do_page_mkwrite+0x1a1/0x5f0 mm/memory.c:2992 wp_page_shared+0x164/0x380 mm/memory.c:3341 handle_pte_fault mm/memory.c:5011 [inline] __handle_mm_fault mm/memory.c:5135 [inline] handle_mm_fault+0x2525/0x5340 mm/memory.c:5256 do_user_addr_fault arch/x86/mm/fault.c:1380 [inline] handle_page_fault arch/x86/mm/fault.c:1471 [inline] exc_page_fault+0x26f/0x660 arch/x86/mm/fault.c:1527 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:570 -> #1 (&mm->mmap_lock){++++}-{3:3}: lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5661 __might_fault+0xbd/0x110 mm/memory.c:5811 reiserfs_ioctl+0x11d/0x340 fs/reiserfs/ioctl.c:96 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl+0xf1/0x160 fs/ioctl.c:856 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+0x63/0xcd -> #0 (&sbi->lock){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain+0x1667/0x58e0 kernel/locking/lockdep.c:3824 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5048 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5661 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x132/0xd80 kernel/locking/mutex.c:747 reiserfs_write_lock+0x76/0xd0 fs/reiserfs/lock.c:27 reiserfs_dirty_inode+0xee/0x240 fs/reiserfs/super.c:704 __mark_inode_dirty+0x331/0xf80 fs/fs-writeback.c:2433 generic_update_time fs/inode.c:1901 [inline] inode_update_time fs/inode.c:1914 [inline] __file_update_time+0x221/0x240 fs/inode.c:2102 file_update_time+0x34c/0x3c0 fs/inode.c:2133 filemap_page_mkwrite+0x275/0x630 mm/filemap.c:3476 do_page_mkwrite+0x1a1/0x5f0 mm/memory.c:2992 wp_page_shared+0x164/0x380 mm/memory.c:3341 handle_pte_fault mm/memory.c:5011 [inline] __handle_mm_fault mm/memory.c:5135 [inline] handle_mm_fault+0x2525/0x5340 mm/memory.c:5256 do_user_addr_fault arch/x86/mm/fault.c:1380 [inline] handle_page_fault arch/x86/mm/fault.c:1471 [inline] exc_page_fault+0x26f/0x660 arch/x86/mm/fault.c:1527 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:570 other info that might help us debug this: Chain exists of: &sbi->lock --> &mm->mmap_lock --> sb_pagefaults#5 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(sb_pagefaults#5); lock(&mm->mmap_lock); lock(sb_pagefaults#5); lock(&sbi->lock); *** DEADLOCK *** 2 locks held by syz-executor.2/12858: #0: ffff88801f7bbd58 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_trylock include/linux/mmap_lock.h:136 [inline] #0: ffff88801f7bbd58 (&mm->mmap_lock){++++}-{3:3}, at: get_mmap_lock_carefully mm/memory.c:5284 [inline] #0: ffff88801f7bbd58 (&mm->mmap_lock){++++}-{3:3}, at: lock_mm_and_find_vma+0x2e/0x2e0 mm/memory.c:5346 #1: ffff88801b7e4558 (sb_pagefaults#5){.+.+}-{0:0}, at: do_page_mkwrite+0x1a1/0x5f0 mm/memory.c:2992 stack backtrace: CPU: 0 PID: 12858 Comm: syz-executor.2 Not tainted 6.1.63-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106 check_noncircular+0x2fa/0x3b0 kernel/locking/lockdep.c:2170 check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain+0x1667/0x58e0 kernel/locking/lockdep.c:3824 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5048 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5661 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x132/0xd80 kernel/locking/mutex.c:747 reiserfs_write_lock+0x76/0xd0 fs/reiserfs/lock.c:27 reiserfs_dirty_inode+0xee/0x240 fs/reiserfs/super.c:704 __mark_inode_dirty+0x331/0xf80 fs/fs-writeback.c:2433 generic_update_time fs/inode.c:1901 [inline] inode_update_time fs/inode.c:1914 [inline] __file_update_time+0x221/0x240 fs/inode.c:2102 file_update_time+0x34c/0x3c0 fs/inode.c:2133 filemap_page_mkwrite+0x275/0x630 mm/filemap.c:3476 do_page_mkwrite+0x1a1/0x5f0 mm/memory.c:2992 wp_page_shared+0x164/0x380 mm/memory.c:3341 handle_pte_fault mm/memory.c:5011 [inline] __handle_mm_fault mm/memory.c:5135 [inline] handle_mm_fault+0x2525/0x5340 mm/memory.c:5256 do_user_addr_fault arch/x86/mm/fault.c:1380 [inline] handle_page_fault arch/x86/mm/fault.c:1471 [inline] exc_page_fault+0x26f/0x660 arch/x86/mm/fault.c:1527 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:570 RIP: 0033:0x7fb7dc44ed2d Code: 48 83 c4 08 4c 89 e8 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f 1f 00 e8 93 cd ff ff eb 8d 90 31 c0 66 0f 1f 44 00 00 41 0f b6 14 04 <88> 14 07 48 83 c0 01 48 39 c3 75 ef 48 01 df 49 01 dc 49 89 7e 28 RSP: 002b:00007ffc0be9a810 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000002 RCX: 0000000000000000 RDX: 0000000000000030 RSI: 00007fb7dc4c787c RDI: 00000000200001c0 RBP: 0000000000000002 R08: 0000000000000000 R09: 0000000000000000 R10: 00000000813282f0 R11: 0000000000000246 R12: 00007fb7dc4c787c R13: 0000000000000002 R14: 00007ffc0be9ada0 R15: 00007ffc0be9aee0