[v5.15] WARNING: kmalloc bug in wnd_init

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 91786f140358 Linux 5.15.175
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12493edf980000
kernel config: https://syzkaller.appspot.com/x/.config?x=792c138814af56fb
dashboard link: https://syzkaller.appspot.com/bug?extid=8511e1e3d2273756d2fd
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12e80dc4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16e80dc4580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/703bce36932e/disk-91786f14.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f72d0cd34063/vmlinux-91786f14.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3ea47692ed8c/Image-91786f14.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/b7f2702f2492/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8511e1...@syzkaller.appspotmail.com

loop0: detected capacity change from 0 to 4096
ntfs3: loop0: Different NTFS' sector size (1024) and media sector size (512)
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4019 at mm/util.c:630 kvmalloc_node+0x1fc/0x204
Modules linked in:
CPU: 0 PID: 4019 Comm: syz-executor121 Not tainted 5.15.175-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : kvmalloc_node+0x1fc/0x204
lr : kvmalloc_node+0x1f8/0x204 mm/util.c:630
sp : ffff80001f9f7770
x29: ffff80001f9f7770 x28: 1fffe0001b8a6468 x27: dfff800000000000
x26: 1ffffffffff80008 x25: 1fffe0001b8a6803 x24: 0000000000008000
x23: 0000000000000000 x22: ffff800009627fb8 x21: 0003ffffffffff02
x20: 00000000ffffffff x19: 0000000000000dc0 x18: 0000000000000000
x17: 0000000000000000 x16: ffff800011b4eaf8 x15: 000000000000000b
x14: 1ffff0000296e06c x13: dfff800000000000 x12: 0000000000000005
x11: 0000000000000000 x10: 0000000000000000 x9 : ffff0000ca4c3680
x8 : ffff80000876d260 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 00000000ffffffff x4 : 0000000000012dc0 x3 : 0004000000000000
x2 : 0003ffffffffff02 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
kvmalloc_node+0x1fc/0x204
kvmalloc include/linux/mm.h:805 [inline]
kvmalloc_array include/linux/mm.h:823 [inline]
wnd_init+0x18c/0x2b0 fs/ntfs3/bitmap.c:670
ntfs_fill_super+0x1d48/0x33b0 fs/ntfs3/super.c:1053
get_tree_bdev+0x360/0x54c fs/super.c:1325
ntfs_fs_get_tree+0x28/0x38 fs/ntfs3/super.c:1354
vfs_get_tree+0x90/0x274 fs/super.c:1530
do_new_mount+0x278/0x8fc fs/namespace.c:3012
path_mount+0x594/0x101c fs/namespace.c:3342
do_mount fs/namespace.c:3355 [inline]
__do_sys_mount fs/namespace.c:3563 [inline]
__se_sys_mount fs/namespace.c:3540 [inline]
__arm64_sys_mount+0x510/0x5e0 fs/namespace.c:3540
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 12248
hardirqs last enabled at (12247): [<ffff800008a75b7c>] bh_lru_install fs/buffer.c:1261 [inline]
hardirqs last enabled at (12247): [<ffff800008a75b7c>] __find_get_block+0xb68/0xdd4 fs/buffer.c:1312
hardirqs last disabled at (12248): [<ffff800011b4a1ac>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (11280): [<ffff8000080309b8>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:31
softirqs last disabled at (11278): [<ffff800008030984>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:18
---[ end trace a09334cf1f19f974 ]---


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup