loop9: detected capacity change from 0 to 4096 ====================================================== WARNING: possible circular locking dependency detected 6.12.0-syzkaller-00239-gc6d64479d609 #0 Not tainted ------------------------------------------------------ syz.9.2926/16136 is trying to acquire lock: ffff88801b074418 (&mm->mmap_lock){++++}-{3:3}, at: __might_fault mm/memory.c:6716 [inline] ffff88801b074418 (&mm->mmap_lock){++++}-{3:3}, at: __might_fault+0xe3/0x190 mm/memory.c:6709 but task is already holding lock: ffff888050985920 (&ni->ni_lock/5){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1109 [inline] ffff888050985920 (&ni->ni_lock/5){+.+.}-{3:3}, at: ntfs_fiemap+0xb6/0x120 fs/ntfs3/file.c:1350 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&ni->ni_lock/5){+.+.}-{3:3}: __mutex_lock_common kernel/locking/mutex.c:608 [inline] __mutex_lock+0x175/0x9c0 kernel/locking/mutex.c:752 ni_lock fs/ntfs3/ntfs_fs.h:1109 [inline] ntfs_truncate fs/ntfs3/file.c:501 [inline] ntfs_setattr+0x4c5/0xc30 fs/ntfs3/file.c:822 notify_change+0x6a9/0x1230 fs/attr.c:552 do_truncate+0x15c/0x220 fs/open.c:65 handle_truncate fs/namei.c:3449 [inline] do_open fs/namei.c:3832 [inline] path_openat+0x2745/0x2d60 fs/namei.c:3987 do_filp_open+0x20c/0x470 fs/namei.c:4014 do_sys_openat2+0x17a/0x1e0 fs/open.c:1398 do_sys_open fs/open.c:1413 [inline] __do_sys_open fs/open.c:1421 [inline] __se_sys_open fs/open.c:1417 [inline] __x64_sys_open+0x154/0x1e0 fs/open.c:1417 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #1 (&sb->s_type->i_mutex_key#35){+.+.}-{3:3}: down_write+0x93/0x200 kernel/locking/rwsem.c:1577 inode_lock include/linux/fs.h:818 [inline] ntfs_file_mmap+0x610/0x780 fs/ntfs3/file.c:377 call_mmap include/linux/fs.h:2183 [inline] mmap_file mm/internal.h:123 [inline] __mmap_region+0x1280/0x21c0 mm/mmap.c:1453 mmap_region+0x270/0x320 mm/mmap.c:1603 do_mmap+0xc00/0xfc0 mm/mmap.c:496 vm_mmap_pgoff+0x1ba/0x360 mm/util.c:588 ksys_mmap_pgoff+0x32c/0x5c0 mm/mmap.c:542 __do_sys_mmap arch/x86/kernel/sys_x86_64.c:86 [inline] __se_sys_mmap arch/x86/kernel/sys_x86_64.c:79 [inline] __x64_sys_mmap+0x125/0x190 arch/x86/kernel/sys_x86_64.c:79 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&mm->mmap_lock){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain kernel/locking/lockdep.c:3904 [inline] __lock_acquire+0x250b/0x3ce0 kernel/locking/lockdep.c:5202 lock_acquire.part.0+0x11b/0x380 kernel/locking/lockdep.c:5825 __might_fault mm/memory.c:6716 [inline] __might_fault+0x11b/0x190 mm/memory.c:6709 _inline_copy_to_user include/linux/uaccess.h:192 [inline] _copy_to_user+0x2d/0xd0 lib/usercopy.c:26 copy_to_user include/linux/uaccess.h:225 [inline] ni_fiemap+0xbe9/0xdb0 fs/ntfs3/frecord.c:2139 ntfs_fiemap+0xc9/0x120 fs/ntfs3/file.c:1352 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x405/0x1990 fs/ioctl.c:840 __do_sys_ioctl fs/ioctl.c:904 [inline] __se_sys_ioctl fs/ioctl.c:892 [inline] __x64_sys_ioctl+0x11d/0x200 fs/ioctl.c:892 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f other info that might help us debug this: Chain exists of: &mm->mmap_lock --> &sb->s_type->i_mutex_key#35 --> &ni->ni_lock/5 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ni->ni_lock/5); lock(&sb->s_type->i_mutex_key#35); lock(&ni->ni_lock/5); rlock(&mm->mmap_lock); *** DEADLOCK *** 1 lock held by syz.9.2926/16136: #0: ffff888050985920 (&ni->ni_lock/5){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1109 [inline] #0: ffff888050985920 (&ni->ni_lock/5){+.+.}-{3:3}, at: ntfs_fiemap+0xb6/0x120 fs/ntfs3/file.c:1350 stack backtrace: CPU: 0 UID: 0 PID: 16136 Comm: syz.9.2926 Not tainted 6.12.0-syzkaller-00239-gc6d64479d609 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_circular_bug+0x41c/0x610 kernel/locking/lockdep.c:2074 check_noncircular+0x31a/0x400 kernel/locking/lockdep.c:2206 check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain kernel/locking/lockdep.c:3904 [inline] __lock_acquire+0x250b/0x3ce0 kernel/locking/lockdep.c:5202 lock_acquire.part.0+0x11b/0x380 kernel/locking/lockdep.c:5825 __might_fault mm/memory.c:6716 [inline] __might_fault+0x11b/0x190 mm/memory.c:6709 _inline_copy_to_user include/linux/uaccess.h:192 [inline] _copy_to_user+0x2d/0xd0 lib/usercopy.c:26 copy_to_user include/linux/uaccess.h:225 [inline] ni_fiemap+0xbe9/0xdb0 fs/ntfs3/frecord.c:2139 ntfs_fiemap+0xc9/0x120 fs/ntfs3/file.c:1352 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x405/0x1990 fs/ioctl.c:840 __do_sys_ioctl fs/ioctl.c:904 [inline] __se_sys_ioctl fs/ioctl.c:892 [inline] __x64_sys_ioctl+0x11d/0x200 fs/ioctl.c:892 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fc86817e759 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fc868ecc038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007fc868335f80 RCX: 00007fc86817e759 RDX: 0000000020000640 RSI: 00000000c020660b RDI: 0000000000000004 RBP: 00007fc8681f175e R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007fc868335f80 R15: 00007ffcb6bd2f98