====================================================== WARNING: possible circular locking dependency detected 6.1.32-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.5/11431 is trying to acquire lock: ffff88807e51e2d8 (&mm->mmap_lock#2){++++}-{3:3}, at: __might_fault+0x8f/0x110 mm/memory.c:5654 but task is already holding lock: ffff888079ffb090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x76/0xd0 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}: lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5669 __mutex_lock_common+0x1d4/0x2520 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799 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:2411 generic_update_time fs/inode.c:1859 [inline] inode_update_time fs/inode.c:1872 [inline] __file_update_time+0x221/0x240 fs/inode.c:2060 file_update_time+0x34c/0x3c0 fs/inode.c:2091 filemap_page_mkwrite+0x275/0x630 mm/filemap.c:3422 do_page_mkwrite+0x1a1/0x5f0 mm/memory.c:2973 wp_page_shared+0x164/0x380 mm/memory.c:3319 handle_pte_fault mm/memory.c:4982 [inline] __handle_mm_fault mm/memory.c:5106 [inline] handle_mm_fault+0x2522/0x5330 mm/memory.c:5227 do_user_addr_fault arch/x86/mm/fault.c:1428 [inline] handle_page_fault arch/x86/mm/fault.c:1519 [inline] exc_page_fault+0x58d/0x790 arch/x86/mm/fault.c:1575 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:570 -> #1 (sb_pagefaults#2){.+.+}-{0:0}: lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5669 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:3421 do_page_mkwrite+0x1a1/0x5f0 mm/memory.c:2973 wp_page_shared+0x164/0x380 mm/memory.c:3319 handle_pte_fault mm/memory.c:4982 [inline] __handle_mm_fault mm/memory.c:5106 [inline] handle_mm_fault+0x2522/0x5330 mm/memory.c:5227 do_user_addr_fault arch/x86/mm/fault.c:1428 [inline] handle_page_fault arch/x86/mm/fault.c:1519 [inline] exc_page_fault+0x58d/0x790 arch/x86/mm/fault.c:1575 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:570 -> #0 (&mm->mmap_lock#2){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3098 [inline] check_prevs_add kernel/locking/lockdep.c:3217 [inline] validate_chain+0x1667/0x58e0 kernel/locking/lockdep.c:3832 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5056 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5669 __might_fault+0xb2/0x110 mm/memory.c:5655 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 other info that might help us debug this: Chain exists of: &mm->mmap_lock#2 --> sb_pagefaults#2 --> &sbi->lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sbi->lock); lock(sb_pagefaults#2); lock(&sbi->lock); lock(&mm->mmap_lock#2); *** DEADLOCK *** 1 lock held by syz-executor.5/11431: #0: ffff888079ffb090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x76/0xd0 fs/reiserfs/lock.c:27 stack backtrace: CPU: 1 PID: 11431 Comm: syz-executor.5 Not tainted 6.1.32-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/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:2178 check_prev_add kernel/locking/lockdep.c:3098 [inline] check_prevs_add kernel/locking/lockdep.c:3217 [inline] validate_chain+0x1667/0x58e0 kernel/locking/lockdep.c:3832 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5056 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5669 __might_fault+0xb2/0x110 mm/memory.c:5655 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 RIP: 0033:0x7f248ce8c169 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f248dbcd168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f248cfabf80 RCX: 00007f248ce8c169 RDX: 00000000200023c0 RSI: 0000000080087601 RDI: 0000000000000005 RBP: 00007f248cee7ca1 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffc637af8df R14: 00007f248dbcd300 R15: 0000000000022000