==================================================================
BUG: KASAN: stack-out-of-bounds in truncate_inode_pages_range+0xd4/0xf64 mm/truncate.c:326
Write of size 248 at addr ffff8000a02a73c0 by task syz-executor.3/12832

CPU: 0 PID: 12832 Comm: syz-executor.3 Not tainted 6.10.0-rc7-syzkaller-00109-gc912bf709078 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
Call trace:
 dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:317
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:324
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:114
 print_address_description mm/kasan/report.c:377 [inline]
 print_report+0x198/0x538 mm/kasan/report.c:488
 kasan_report+0xd8/0x138 mm/kasan/report.c:601
 kasan_check_range+0x268/0x2a8 mm/kasan/generic.c:189
 __asan_memset+0x34/0x64 mm/kasan/shadow.c:84
 truncate_inode_pages_range+0xd4/0xf64 mm/truncate.c:326
 truncate_inode_pages mm/truncate.c:439 [inline]
 truncate_inode_pages_final+0x90/0xc0 mm/truncate.c:474
 ntfs_evict_inode+0x20/0x48 fs/ntfs3/inode.c:1832
 evict+0x260/0x68c fs/inode.c:667
 iput_final fs/inode.c:1741 [inline]
 iput+0x74c/0x830 fs/inode.c:1767
 ntfs_fill_super+0x3250/0x3a94 fs/ntfs3/super.c:1480
 get_tree_bdev+0x320/0x470 fs/super.c:1624
 ntfs_fs_get_tree+0x28/0x38 fs/ntfs3/super.c:1703
 vfs_get_tree+0x90/0x288 fs/super.c:1789
 do_new_mount+0x278/0x900 fs/namespace.c:3352
 path_mount+0x590/0xe04 fs/namespace.c:3679
 do_mount fs/namespace.c:3692 [inline]
 __do_sys_mount fs/namespace.c:3898 [inline]
 __se_sys_mount fs/namespace.c:3875 [inline]
 __arm64_sys_mount+0x3c4/0x488 fs/namespace.c:3875
 __invoke_syscall arch/arm64/kernel/syscall.c:34 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:48
 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:131
 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:150
 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:712
 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730
 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598

The buggy address belongs to stack of task syz-executor.3/12832
 and is located at offset 352 in frame:
 const_folio_flags include/linux/page-flags.h:312 [inline]
 folio_test_head include/linux/page-flags.h:836 [inline]
 folio_test_large include/linux/page-flags.h:857 [inline]
 folio_nr_pages include/linux/mm.h:2079 [inline]
 truncate_inode_pages_range+0x0/0xf64 mm/truncate.c:288

This frame has 3 objects:
 [32, 288) 'fbatch'
 [352, 600) 'indices'
 [672, 680) 'index'

The buggy address belongs to the virtual mapping at
 [ffff8000a02a0000, ffff8000a02a9000) created by:
 copy_process+0x498/0x31d0 kernel/fork.c:2220

The buggy address belongs to the physical page:
page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x4 pfn:0x10fc27
memcg:ffff0000c5bba282
flags: 0x5ffc00000000000(node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000000000 0000000000000000 dead000000000122 0000000000000000
raw: 0000000000000004 0000000000000000 00000001ffffffff ffff0000c5bba282
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff8000a02a7300: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff8000a02a7380: f2 f2 f2 f2 f2 f2 f2 f2 00 00 00 00 00 00 00 00
>ffff8000a02a7400: 00 00 00 f3 00 00 00 00 00 00 00 00 00 00 00 00
                            ^
 ffff8000a02a7480: 00 00 00 00 00 00 00 f2 f2 f2 f2 f2 f2 f2 f2 f2
 ffff8000a02a7500: 00 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================