loop0: detected capacity change from 0 to 32768 loop0: detected capacity change from 0 to 4096 ====================================================== WARNING: possible circular locking dependency detected 6.12.0-syzkaller-g7b1d1d4cfac0 #0 Not tainted ------------------------------------------------------ syz.0.207/7686 is trying to acquire lock: ffff0000f309ad10 (&ni->ni_lock#3/5){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1109 [inline] ffff0000f309ad10 (&ni->ni_lock#3/5){+.+.}-{3:3}, at: ntfs_fallocate+0x6b0/0xfd0 fs/ntfs3/file.c:664 but task is already holding lock: ffff0000f309b148 (mapping.invalidate_lock#5){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:860 [inline] ffff0000f309b148 (mapping.invalidate_lock#5){++++}-{3:3}, at: ntfs_fallocate+0x39c/0xfd0 fs/ntfs3/file.c:594 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (mapping.invalidate_lock#5){++++}-{3:3}: down_read+0x58/0x2fc kernel/locking/rwsem.c:1524 filemap_invalidate_lock_shared include/linux/fs.h:870 [inline] filemap_fault+0x5c0/0x138c mm/filemap.c:3331 __do_fault+0x11c/0x374 mm/memory.c:4882 do_shared_fault mm/memory.c:5361 [inline] do_fault mm/memory.c:5435 [inline] do_pte_missing mm/memory.c:3965 [inline] handle_pte_fault mm/memory.c:5766 [inline] __handle_mm_fault+0x1d50/0x66e8 mm/memory.c:5909 handle_mm_fault+0x29c/0x8b4 mm/memory.c:6077 do_page_fault+0x404/0x10a8 arch/arm64/mm/fault.c:647 do_translation_fault+0xc4/0x114 arch/arm64/mm/fault.c:783 do_mem_abort+0x74/0x200 arch/arm64/mm/fault.c:919 el0_da+0x60/0x178 arch/arm64/kernel/entry-common.c:604 el0t_64_sync_handler+0xcc/0x108 arch/arm64/kernel/entry-common.c:765 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600 -> #2 (&vma->vm_lock->lock){++++}-{3:3}: down_write+0x50/0xc0 kernel/locking/rwsem.c:1577 vma_start_write include/linux/mm.h:769 [inline] vma_link+0x248/0x49c mm/vma.c:1600 insert_vm_struct+0x284/0x378 mm/mmap.c:1995 __bprm_mm_init fs/exec.c:289 [inline] bprm_mm_init fs/exec.c:393 [inline] alloc_bprm+0x6dc/0xb68 fs/exec.c:1548 kernel_execve+0xa4/0x820 fs/exec.c:1977 run_init_process+0x1bc/0x1ec init/main.c:1390 try_to_run_init_process init/main.c:1397 [inline] kernel_init+0xdc/0x2a0 init/main.c:1525 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:862 -> #1 (&mm->mmap_lock){++++}-{3:3}: __might_fault+0xc4/0x124 mm/memory.c:6716 _inline_copy_to_user include/linux/uaccess.h:192 [inline] copy_to_user include/linux/uaccess.h:223 [inline] ni_fiemap+0x1134/0x1444 fs/ntfs3/frecord.c:2139 ntfs_fiemap+0x110/0x168 fs/ntfs3/file.c:1352 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x1de8/0x2aa8 fs/ioctl.c:841 __do_sys_ioctl fs/ioctl.c:905 [inline] __se_sys_ioctl fs/ioctl.c:893 [inline] __arm64_sys_ioctl+0xe4/0x1c8 fs/ioctl.c:893 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600 -> #0 (&ni->ni_lock#3/5){+.+.}-{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+0x33f8/0x77c8 kernel/locking/lockdep.c:5202 lock_acquire+0x240/0x728 kernel/locking/lockdep.c:5825 __mutex_lock_common+0x190/0x21a0 kernel/locking/mutex.c:608 __mutex_lock kernel/locking/mutex.c:752 [inline] mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:804 ni_lock fs/ntfs3/ntfs_fs.h:1109 [inline] ntfs_fallocate+0x6b0/0xfd0 fs/ntfs3/file.c:664 vfs_fallocate+0x484/0x5c0 fs/open.c:333 ksys_fallocate fs/open.c:356 [inline] __do_sys_fallocate fs/open.c:364 [inline] __se_sys_fallocate fs/open.c:362 [inline] __arm64_sys_fallocate+0xc0/0x110 fs/open.c:362 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600 other info that might help us debug this: Chain exists of: &ni->ni_lock#3/5 --> &vma->vm_lock->lock --> mapping.invalidate_lock#5 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(mapping.invalidate_lock#5); lock(&vma->vm_lock->lock); lock(mapping.invalidate_lock#5); lock(&ni->ni_lock#3/5); *** DEADLOCK *** 3 locks held by syz.0.207/7686: #0: ffff0000c71d4420 (sb_writers#25){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2931 [inline] #0: ffff0000c71d4420 (sb_writers#25){.+.+}-{0:0}, at: vfs_fallocate+0x428/0x5c0 fs/open.c:332 #1: ffff0000f309afa8 (&sb->s_type->i_mutex_key#30){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:815 [inline] #1: ffff0000f309afa8 (&sb->s_type->i_mutex_key#30){+.+.}-{3:3}, at: ntfs_fallocate+0x2dc/0xfd0 fs/ntfs3/file.c:580 #2: ffff0000f309b148 (mapping.invalidate_lock#5){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:860 [inline] #2: ffff0000f309b148 (mapping.invalidate_lock#5){++++}-{3:3}, at: ntfs_fallocate+0x39c/0xfd0 fs/ntfs3/file.c:594 stack backtrace: CPU: 0 UID: 0 PID: 7686 Comm: syz.0.207 Not tainted 6.12.0-syzkaller-g7b1d1d4cfac0 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Call trace: show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:484 (C) __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:120 dump_stack+0x1c/0x28 lib/dump_stack.c:129 print_circular_bug+0x154/0x1c0 kernel/locking/lockdep.c:2074 check_noncircular+0x310/0x404 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+0x33f8/0x77c8 kernel/locking/lockdep.c:5202 lock_acquire+0x240/0x728 kernel/locking/lockdep.c:5825 __mutex_lock_common+0x190/0x21a0 kernel/locking/mutex.c:608 __mutex_lock kernel/locking/mutex.c:752 [inline] mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:804 ni_lock fs/ntfs3/ntfs_fs.h:1109 [inline] ntfs_fallocate+0x6b0/0xfd0 fs/ntfs3/file.c:664 vfs_fallocate+0x484/0x5c0 fs/open.c:333 ksys_fallocate fs/open.c:356 [inline] __do_sys_fallocate fs/open.c:364 [inline] __se_sys_fallocate fs/open.c:362 [inline] __arm64_sys_fallocate+0xc0/0x110 fs/open.c:362 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600 netlink: 'syz.0.207': attribute type 10 has an invalid length. netlink: 40 bytes leftover after parsing attributes in process `syz.0.207'. batman_adv: batadv0: Adding interface: wlan0 batman_adv: batadv0: The MTU of interface wlan0 is too small (1500) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1560 would solve the problem. batman_adv: batadv0: Interface activated: wlan0