====================================================== WARNING: possible circular locking dependency detected 6.3.0-next-20230425-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.2/17710 is trying to acquire lock: ffff88802adc6090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x79/0x100 fs/reiserfs/lock.c:27 but task is already holding lock: ffff88802964c558 (sb_pagefaults#4){.+.+}-{0:0}, at: do_page_mkwrite+0x1a1/0x690 mm/memory.c:2935 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (sb_pagefaults#4){.+.+}-{0:0}: percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1494 [inline] sb_start_pagefault include/linux/fs.h:1598 [inline] filemap_page_mkwrite+0x174/0x790 mm/filemap.c:3566 do_page_mkwrite+0x1a1/0x690 mm/memory.c:2935 wp_page_shared mm/memory.c:3284 [inline] do_wp_page+0x356/0x3490 mm/memory.c:3366 handle_pte_fault mm/memory.c:4968 [inline] __handle_mm_fault+0x1693/0x3c70 mm/memory.c:5093 handle_mm_fault+0x2af/0x9f0 mm/memory.c:5247 do_user_addr_fault+0x53d/0x1240 arch/x86/mm/fault.c:1462 handle_page_fault arch/x86/mm/fault.c:1556 [inline] exc_page_fault+0x98/0x170 arch/x86/mm/fault.c:1612 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570 -> #1 (&mm->mmap_lock){++++}-{3:3}: __might_fault mm/memory.c:5736 [inline] __might_fault+0x115/0x190 mm/memory.c:5729 reiserfs_ioctl+0x1d2/0x330 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] __x64_sys_ioctl+0x197/0x210 fs/ioctl.c:856 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x39/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:3108 [inline] check_prevs_add kernel/locking/lockdep.c:3227 [inline] validate_chain kernel/locking/lockdep.c:3842 [inline] __lock_acquire+0x2f21/0x5df0 kernel/locking/lockdep.c:5074 lock_acquire.part.0+0x11c/0x370 kernel/locking/lockdep.c:5691 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x12f/0x1350 kernel/locking/mutex.c:747 reiserfs_write_lock+0x79/0x100 fs/reiserfs/lock.c:27 reiserfs_dirty_inode+0xd2/0x260 fs/reiserfs/super.c:704 __mark_inode_dirty+0x1e0/0xd60 fs/fs-writeback.c:2424 generic_update_time+0x21b/0x2b0 fs/inode.c:1859 inode_update_time fs/inode.c:1872 [inline] __file_update_time fs/inode.c:2057 [inline] file_update_time+0x224/0x270 fs/inode.c:2088 filemap_page_mkwrite+0x28c/0x790 mm/filemap.c:3567 do_page_mkwrite+0x1a1/0x690 mm/memory.c:2935 wp_page_shared mm/memory.c:3284 [inline] do_wp_page+0x356/0x3490 mm/memory.c:3366 handle_pte_fault mm/memory.c:4968 [inline] __handle_mm_fault+0x1693/0x3c70 mm/memory.c:5093 handle_mm_fault+0x2af/0x9f0 mm/memory.c:5247 do_user_addr_fault+0x53d/0x1240 arch/x86/mm/fault.c:1462 handle_page_fault arch/x86/mm/fault.c:1556 [inline] exc_page_fault+0x98/0x170 arch/x86/mm/fault.c:1612 asm_exc_page_fault+0x26/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#4 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- rlock(sb_pagefaults#4); lock(&mm->mmap_lock); lock(sb_pagefaults#4); lock(&sbi->lock); *** DEADLOCK *** 2 locks held by syz-executor.2/17710: #0: ffff88807f520a68 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_trylock include/linux/mmap_lock.h:161 [inline] #0: ffff88807f520a68 (&mm->mmap_lock){++++}-{3:3}, at: do_user_addr_fault+0x46b/0x1240 arch/x86/mm/fault.c:1403 #1: ffff88802964c558 (sb_pagefaults#4){.+.+}-{0:0}, at: do_page_mkwrite+0x1a1/0x690 mm/memory.c:2935 stack backtrace: CPU: 1 PID: 17710 Comm: syz-executor.2 Not tainted 6.3.0-next-20230425-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106 check_noncircular+0x25f/0x2e0 kernel/locking/lockdep.c:2188 check_prev_add kernel/locking/lockdep.c:3108 [inline] check_prevs_add kernel/locking/lockdep.c:3227 [inline] validate_chain kernel/locking/lockdep.c:3842 [inline] __lock_acquire+0x2f21/0x5df0 kernel/locking/lockdep.c:5074 lock_acquire.part.0+0x11c/0x370 kernel/locking/lockdep.c:5691 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x12f/0x1350 kernel/locking/mutex.c:747 reiserfs_write_lock+0x79/0x100 fs/reiserfs/lock.c:27 reiserfs_dirty_inode+0xd2/0x260 fs/reiserfs/super.c:704 __mark_inode_dirty+0x1e0/0xd60 fs/fs-writeback.c:2424 generic_update_time+0x21b/0x2b0 fs/inode.c:1859 inode_update_time fs/inode.c:1872 [inline] __file_update_time fs/inode.c:2057 [inline] file_update_time+0x224/0x270 fs/inode.c:2088 filemap_page_mkwrite+0x28c/0x790 mm/filemap.c:3567 do_page_mkwrite+0x1a1/0x690 mm/memory.c:2935 wp_page_shared mm/memory.c:3284 [inline] do_wp_page+0x356/0x3490 mm/memory.c:3366 handle_pte_fault mm/memory.c:4968 [inline] __handle_mm_fault+0x1693/0x3c70 mm/memory.c:5093 handle_mm_fault+0x2af/0x9f0 mm/memory.c:5247 do_user_addr_fault+0x53d/0x1240 arch/x86/mm/fault.c:1462 handle_page_fault arch/x86/mm/fault.c:1556 [inline] exc_page_fault+0x98/0x170 arch/x86/mm/fault.c:1612 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570 RIP: 0033:0x7fd930886bcf Code: d0 eb 0b 0f 1f 84 00 00 00 00 00 48 89 f8 48 83 fa 10 0f 82 da 00 00 00 48 83 fa 20 0f 87 1f 01 00 00 0f 10 06 0f 10 4c 16 f0 <0f> 11 07 0f 11 4c 17 f0 c3 0f 1f 84 00 00 00 00 00 48 39 d1 0f 82 RSP: 002b:00007ffd8a1392d8 EFLAGS: 00010283 RAX: 0000000020000040 RBX: 0000000000000000 RCX: 00007fd930400000 RDX: 0000000000000012 RSI: 00007fd930401e50 RDI: 0000000020000040 RBP: 00007ffd8a139398 R08: 00007fd930800000 R09: 00007fd930400000 R10: 00007fd930401e38 R11: 0000000000000246 R12: 00000000001a5e9e R13: 00007ffd8a1393c0 R14: 00007fd9309ac120 R15: 0000000000000032