[v6.1] WARNING in ni_fiemap

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: aa4cd140bba5 Linux 6.1.112
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1064ab27980000
kernel config: https://syzkaller.appspot.com/x/.config?x=33931c04473f8585
dashboard link: https://syzkaller.appspot.com/bug?extid=a9793b666ed63ca761e9
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2a9778339706/disk-aa4cd140.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b568a6da8a9b/vmlinux-aa4cd140.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3c56af7eb2c4/bzImage-aa4cd140.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 3974 at mm/page_alloc.c:5534 __alloc_pages+0x3b7/0x770 mm/page_alloc.c:5534
Modules linked in:
CPU: 0 PID: 3974 Comm: syz.4.55 Not tainted 6.1.112-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:__alloc_pages+0x3b7/0x770 mm/page_alloc.c:5534
Code: fc ff df 0f 85 fa 00 00 00 44 89 e9 81 e1 7f ff ff ff a9 00 00 04 00 41 0f 44 cd 41 89 cd e9 ea 00 00 00 c6 05 2a 54 af 0c 01 <0f> 0b 41 83 fc 0a 0f 86 1e fd ff ff 45 31 e4 48 c7 44 24 20 0e 36
RSP: 0018:ffffc9000319f660 EFLAGS: 00010246
RAX: 0000000000000000 RBX: dffffc0000000000 RCX: 0000000000000000
RDX: 0000000000000028 RSI: 0000000000000000 RDI: ffffc9000319f6e8
RBP: ffffc9000319f778 R08: dffffc0000000000 R09: ffffc9000319f6c0
R10: 0000000000000000 R11: dffffc0000000001 R12: 000000000000000d
R13: 0000000000040d40 R14: 1ffff92000633ed4 R15: 1ffff92000633ed0
FS: 00007f6fbe1bd6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb736806f98 CR3: 00000000689eb000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__alloc_pages_node include/linux/gfp.h:237 [inline]
alloc_pages_node include/linux/gfp.h:260 [inline]
__kmalloc_large_node+0x91/0x1d0 mm/slab_common.c:1077
__do_kmalloc_node mm/slab_common.c:924 [inline]
__kmalloc+0x118/0x230 mm/slab_common.c:949
kmalloc_array include/linux/slab.h:609 [inline]
ni_fiemap+0x3b0/0x1900 fs/ntfs3/frecord.c:2005
ntfs_fiemap+0x12e/0x170 fs/ntfs3/file.c:1244
ioctl_fiemap fs/ioctl.c:219 [inline]
do_vfs_ioctl+0x18e9/0x2a90 fs/ioctl.c:810
__do_sys_ioctl fs/ioctl.c:868 [inline]
__se_sys_ioctl+0x81/0x160 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f6fbd37dff9
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:00007f6fbe1bd038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f6fbd535f80 RCX: 00007f6fbd37dff9
RDX: 0000000020000880 RSI: 00000000c020660b RDI: 0000000000000004
RBP: 00007f6fbd3f0296 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f6fbd535f80 R15: 00007ffc483574f8
</TASK>


---
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 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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: e4d90d63d385 Linux 6.1.119
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1429c0df980000
kernel config: https://syzkaller.appspot.com/x/.config?x=393f8074c5fb7ad6

dashboard link: https://syzkaller.appspot.com/bug?extid=a9793b666ed63ca761e9
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=13693f78580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16e0a7c0580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3986cbf4f35a/disk-e4d90d63.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d2963d16cebb/vmlinux-e4d90d63.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a877a1a23701/Image-e4d90d63.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/4c0f8673e3c6/mount_0.gz

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

loop0: detected capacity change from 0 to 4096
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4289 at mm/page_alloc.c:5566 __alloc_pages+0x32c/0x730 mm/page_alloc.c:5566
Modules linked in:
CPU: 0 PID: 4289 Comm: syz-executor256 Not tainted 6.1.119-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024

pstate: 20400005 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __alloc_pages+0x32c/0x730 mm/page_alloc.c:5566
lr : __alloc_pages+0xc8/0x730 mm/page_alloc.c:5560
sp : ffff800021337580
x29: ffff800021337670 x28: ffff8000213375a0 x27: dfff800000000000
x26: ffff700004266eb4 x25: 0000000000000000 x24: ffff8000213375c0
x23: 0000000000000000 x22: 0000000000040d40 x21: 1ffff00004266eb8
x20: ffff8000213375e0 x19: 000000000000000e x18: ffff800021337480
x17: ffff800018b6a000 x16: ffff800012272dc0 x15: 0000000000000000
x14: 0000000000000001 x13: ffff0000d9249bc0 x12: 0000000000000005
x11: 1ffff00004266ebc x10: 0000000000000000 x9 : 0000000000000001
x8 : ffff8000183fc000 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000020
x2 : 0000000000000008 x1 : 0000000000000000 x0 : ffff8000213375e0
Call trace:
__alloc_pages+0x32c/0x730 mm/page_alloc.c:5566

__alloc_pages_node include/linux/gfp.h:237 [inline]
alloc_pages_node include/linux/gfp.h:260 [inline]

__kmalloc_large_node+0xbc/0x21c mm/slab_common.c:1077
__do_kmalloc_node mm/slab_common.c:924 [inline]
__kmalloc+0x130/0x1c4 mm/slab_common.c:949
kmalloc_array include/linux/slab.h:609 [inline]
ni_fiemap+0x2a0/0x1444 fs/ntfs3/frecord.c:2005
ntfs_fiemap+0x110/0x168 fs/ntfs3/file.c:1254
ioctl_fiemap fs/ioctl.c:219 [inline]
do_vfs_ioctl+0x194c/0x26f8 fs/ioctl.c:810
__do_sys_ioctl fs/ioctl.c:868 [inline]
__se_sys_ioctl fs/ioctl.c:856 [inline]
__arm64_sys_ioctl+0xe4/0x1c8 fs/ioctl.c:856
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
irq event stamp: 29044
hardirqs last enabled at (29043): [<ffff800008975210>] kasan_quarantine_put+0xdc/0x204 mm/kasan/quarantine.c:242
hardirqs last disabled at (29044): [<ffff800012320d2c>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (28348): [<ffff800008030310>] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32
softirqs last disabled at (28346): [<ffff8000080302dc>] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19
---[ end trace 0000000000000000 ]---


---
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.