====================================================== WARNING: possible circular locking dependency detected 6.6.0-syzkaller-03860-g5a6a09e97199 #0 Not tainted ------------------------------------------------------ syz-executor.5/2666 is trying to acquire lock: ffff88804afd7090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x7a/0xd0 fs/reiserfs/lock.c:27 but task is already holding lock: ffff8880146da510 (sb_pagefaults#8){.+.+}-{0:0}, at: do_page_mkwrite+0x197/0x470 mm/memory.c:2934 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (sb_pagefaults#8){.+.+}-{0:0}: percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1635 [inline] sb_start_pagefault include/linux/fs.h:1739 [inline] filemap_page_mkwrite+0x16f/0x640 mm/filemap.c:3628 do_page_mkwrite+0x197/0x470 mm/memory.c:2934 wp_page_shared mm/memory.c:3294 [inline] do_wp_page+0xf87/0x4190 mm/memory.c:3379 handle_pte_fault mm/memory.c:4997 [inline] __handle_mm_fault mm/memory.c:5122 [inline] handle_mm_fault+0x1b45/0x62b0 mm/memory.c:5287 do_user_addr_fault arch/x86/mm/fault.c:1413 [inline] handle_page_fault arch/x86/mm/fault.c:1505 [inline] exc_page_fault+0x2ac/0x860 arch/x86/mm/fault.c:1561 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570 -> #1 (&mm->mmap_lock){++++}-{3:3}: __might_fault+0xc1/0x120 mm/memory.c:5899 reiserfs_ioctl+0x125/0x2f0 fs/reiserfs/ioctl.c:96 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:871 [inline] __se_sys_ioctl+0xf8/0x170 fs/ioctl.c:857 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x44/0x110 arch/x86/entry/common.c:82 entry_SYSCALL_64_after_hwframe+0x63/0x6b -> #0 (&sbi->lock){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3868 [inline] __lock_acquire+0x39ff/0x7f70 kernel/locking/lockdep.c:5136 lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5753 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x136/0xd60 kernel/locking/mutex.c:747 reiserfs_write_lock+0x7a/0xd0 fs/reiserfs/lock.c:27 reiserfs_dirty_inode+0xf2/0x240 fs/reiserfs/super.c:704 __mark_inode_dirty+0x305/0xd90 fs/fs-writeback.c:2452 generic_update_time fs/inode.c:1941 [inline] inode_update_time fs/inode.c:1954 [inline] __file_update_time fs/inode.c:2142 [inline] file_update_time+0x191/0x1b0 fs/inode.c:2172 filemap_page_mkwrite+0x27b/0x640 mm/filemap.c:3629 do_page_mkwrite+0x197/0x470 mm/memory.c:2934 wp_page_shared mm/memory.c:3294 [inline] do_wp_page+0xf87/0x4190 mm/memory.c:3379 handle_pte_fault mm/memory.c:4997 [inline] __handle_mm_fault mm/memory.c:5122 [inline] handle_mm_fault+0x1b45/0x62b0 mm/memory.c:5287 do_user_addr_fault arch/x86/mm/fault.c:1413 [inline] handle_page_fault arch/x86/mm/fault.c:1505 [inline] exc_page_fault+0x2ac/0x860 arch/x86/mm/fault.c:1561 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#8 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- rlock(sb_pagefaults#8); lock(&mm->mmap_lock); lock(sb_pagefaults#8); lock(&sbi->lock); *** DEADLOCK *** 2 locks held by syz-executor.5/2666: #0: ffff88807cfa14a0 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_trylock include/linux/mmap_lock.h:165 [inline] #0: ffff88807cfa14a0 (&mm->mmap_lock){++++}-{3:3}, at: get_mmap_lock_carefully mm/memory.c:5314 [inline] #0: ffff88807cfa14a0 (&mm->mmap_lock){++++}-{3:3}, at: lock_mm_and_find_vma+0x32/0x2d0 mm/memory.c:5374 #1: ffff8880146da510 (sb_pagefaults#8){.+.+}-{0:0}, at: do_page_mkwrite+0x197/0x470 mm/memory.c:2934 stack backtrace: CPU: 0 PID: 2666 Comm: syz-executor.5 Not tainted 6.6.0-syzkaller-03860-g5a6a09e97199 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106 check_noncircular+0x375/0x4a0 kernel/locking/lockdep.c:2187 check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3868 [inline] __lock_acquire+0x39ff/0x7f70 kernel/locking/lockdep.c:5136 lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5753 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x136/0xd60 kernel/locking/mutex.c:747 reiserfs_write_lock+0x7a/0xd0 fs/reiserfs/lock.c:27 reiserfs_dirty_inode+0xf2/0x240 fs/reiserfs/super.c:704 __mark_inode_dirty+0x305/0xd90 fs/fs-writeback.c:2452 generic_update_time fs/inode.c:1941 [inline] inode_update_time fs/inode.c:1954 [inline] __file_update_time fs/inode.c:2142 [inline] file_update_time+0x191/0x1b0 fs/inode.c:2172 filemap_page_mkwrite+0x27b/0x640 mm/filemap.c:3629 do_page_mkwrite+0x197/0x470 mm/memory.c:2934 wp_page_shared mm/memory.c:3294 [inline] do_wp_page+0xf87/0x4190 mm/memory.c:3379 handle_pte_fault mm/memory.c:4997 [inline] __handle_mm_fault mm/memory.c:5122 [inline] handle_mm_fault+0x1b45/0x62b0 mm/memory.c:5287 do_user_addr_fault arch/x86/mm/fault.c:1413 [inline] handle_page_fault arch/x86/mm/fault.c:1505 [inline] exc_page_fault+0x2ac/0x860 arch/x86/mm/fault.c:1561 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570 RIP: 0033:0x7ff7f845db98 Code: fc 89 37 c3 c5 fa 6f 06 c5 fa 6f 4c 16 f0 c5 fa 7f 07 c5 fa 7f 4c 17 f0 c3 66 0f 1f 84 00 00 00 00 00 48 8b 4c 16 f8 48 8b 36 <48> 89 37 48 89 4c 17 f8 c3 c5 fe 6f 54 16 e0 c5 fe 6f 5c 16 c0 c5 RSP: 002b:00007ffca663cae8 EFLAGS: 00010206 RAX: 0000000020000280 RBX: 00007ffca663cbf8 RCX: 006c6c61206b636f RDX: 000000000000000b RSI: 61206b636f6c6e75 RDI: 0000000020000280 RBP: 0000000000000032 R08: 00007ff7f8400000 R09: 00007ffca66cc0b0 R10: 00007ffca66cc080 R11: 000000000005b1ca R12: 00007ff7f8001470 R13: fffffffffffffffe R14: 00007ff7f8000000 R15: 00007ff7f8001478