======================================================
WARNING: possible circular locking dependency detected
5.15.180-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor.5/4881 is trying to acquire lock:
ffff88806fea4090 (&sbi->lock
){+.+.}-{3:3}, at: reiserfs_write_lock+0x6b/0xe0 fs/reiserfs/lock.c:27

but task is already holding lock:
ffff8880122b1628 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
ffff8880122b1628 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x12e/0x200 mm/util.c:549

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&mm->mmap_lock){++++}-{3:3}:
       __might_fault mm/memory.c:5357 [inline]
       __might_fault+0xe8/0x160 mm/memory.c:5342
       reiserfs_ioctl+0x1f2/0x290 fs/reiserfs/ioctl.c:96
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:874 [inline]
       __se_sys_ioctl fs/ioctl.c:860 [inline]
       __x64_sys_ioctl+0x11f/0x190 fs/ioctl.c:860
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x33/0x80 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #0 (&sbi->lock){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3053 [inline]
       check_prevs_add kernel/locking/lockdep.c:3172 [inline]
       validate_chain kernel/locking/lockdep.c:3788 [inline]
       __lock_acquire+0x2a3d/0x55a0 kernel/locking/lockdep.c:5012
       lock_acquire kernel/locking/lockdep.c:5623 [inline]
       lock_acquire+0x19d/0x4b0 kernel/locking/lockdep.c:5588
       __mutex_lock_common kernel/locking/mutex.c:596 [inline]
       __mutex_lock+0x12c/0x12d0 kernel/locking/mutex.c:729
       reiserfs_write_lock+0x6b/0xe0 fs/reiserfs/lock.c:27
       reiserfs_dirty_inode+0xb3/0x210 fs/reiserfs/super.c:704
       __mark_inode_dirty+0x149/0xa30 fs/fs-writeback.c:2464
       generic_update_time fs/inode.c:1881 [inline]
       inode_update_time fs/inode.c:1894 [inline]
       touch_atime+0x4db/0x5a0 fs/inode.c:1966
       file_accessed include/linux/fs.h:2521 [inline]
       generic_file_mmap+0xe8/0x120 mm/filemap.c:3401
       call_mmap include/linux/fs.h:2177 [inline]
       mmap_file+0x54/0xb0 mm/util.c:1092
       __mmap_region mm/mmap.c:1784 [inline]
       mmap_region+0x900/0x1000 mm/mmap.c:2921
       do_mmap+0x5ca/0xd80 mm/mmap.c:1574
       vm_mmap_pgoff+0x160/0x200 mm/util.c:551
       ksys_mmap_pgoff+0x3b5/0x5f0 mm/mmap.c:1623
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x33/0x80 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&mm->mmap_lock
);
                               lock(&sbi->lock);
                               lock(&mm->mmap_lock);
  lock(&sbi->lock);

 *** DEADLOCK ***

2 locks held by syz-executor.5/4881:
 #0: ffff8880122b1628 (
&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x12e/0x200 mm/util.c:549
 #1: ffff888012804448 (sb_writers#13
){.+.+}-{0:0}, at: file_accessed include/linux/fs.h:2521 [inline]
){.+.+}-{0:0}, at: generic_file_mmap+0xe8/0x120 mm/filemap.c:3401

stack backtrace:
CPU: 0 PID: 4881 Comm: syz-executor.5 Not tainted 5.15.180-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x57/0x7d lib/dump_stack.c:106
 check_noncircular+0x25f/0x2e0 kernel/locking/lockdep.c:2133
 check_prev_add kernel/locking/lockdep.c:3053 [inline]
 check_prevs_add kernel/locking/lockdep.c:3172 [inline]
 validate_chain kernel/locking/lockdep.c:3788 [inline]
 __lock_acquire+0x2a3d/0x55a0 kernel/locking/lockdep.c:5012
 lock_acquire kernel/locking/lockdep.c:5623 [inline]
 lock_acquire+0x19d/0x4b0 kernel/locking/lockdep.c:5588
 __mutex_lock_common kernel/locking/mutex.c:596 [inline]
 __mutex_lock+0x12c/0x12d0 kernel/locking/mutex.c:729
 reiserfs_write_lock+0x6b/0xe0 fs/reiserfs/lock.c:27
 reiserfs_dirty_inode+0xb3/0x210 fs/reiserfs/super.c:704
 __mark_inode_dirty+0x149/0xa30 fs/fs-writeback.c:2464
 generic_update_time fs/inode.c:1881 [inline]
 inode_update_time fs/inode.c:1894 [inline]
 touch_atime+0x4db/0x5a0 fs/inode.c:1966
 file_accessed include/linux/fs.h:2521 [inline]
 generic_file_mmap+0xe8/0x120 mm/filemap.c:3401
 call_mmap include/linux/fs.h:2177 [inline]
 mmap_file+0x54/0xb0 mm/util.c:1092
 __mmap_region mm/mmap.c:1784 [inline]
 mmap_region+0x900/0x1000 mm/mmap.c:2921
 do_mmap+0x5ca/0xd80 mm/mmap.c:1574
 vm_mmap_pgoff+0x160/0x200 mm/util.c:551
 ksys_mmap_pgoff+0x3b5/0x5f0 mm/mmap.c:1623
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x33/0x80 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fb6456ebb29
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fb64526e0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
RAX: ffffffffffffffda RBX: 00007fb64580af80 RCX: 00007fb6456ebb29
RDX: 0000000000000002 RSI: 0000000000b36000 RDI: 0000000020000000
RBP: 00007fb64573747a R08: 0000000000000006 R09: 0000000000000000
R10: 0000000000028011 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000006 R14: 00007fb64580af80 R15: 00007ffe5bca0628
 </TASK>