[v5.15] WARNING in create_strip_zones

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 91d48252ad4b Linux 5.15.202
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1249ff94580000
kernel config: https://syzkaller.appspot.com/x/.config?x=353ae28c40b35af5
dashboard link: https://syzkaller.appspot.com/bug?extid=c7c2b490dd2cbc338e1d
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/74e75dfcb812/disk-91d48252.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bfa72aab00f2/vmlinux-91d48252.xz
kernel image: https://storage.googleapis.com/syzbot-assets/47ea72d1c7dc/bzImage-91d48252.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 4938 at mm/page_alloc.c:5476 current_gfp_context include/linux/sched/mm.h:-1 [inline]
WARNING: CPU: 1 PID: 4938 at mm/page_alloc.c:5476 __alloc_pages+0x39f/0x480 mm/page_alloc.c:5488
Modules linked in:
CPU: 1 PID: 4938 Comm: syz.2.219 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
RIP: 0010:__alloc_pages+0x39f/0x480 mm/page_alloc.c:5476
Code: 31 ff e9 b1 fe ff ff e8 ff fe 07 08 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 4f fd ff ff 4c 89 e7 e8 86 c2 09 00 e9 42 fd ff ff <0f> 0b 45 31 ff e9 ee fe ff ff 65 44 8b 2d 67 ab 4d 7e 41 83 fd 08
RSP: 0018:ffffc9000329f2e0 EFLAGS: 00010246
RAX: ffffc9000329f320 RBX: 1ffff92000653e60 RCX: 0000000000000000
RDX: 0000000000000028 RSI: 0000000000000000 RDI: ffffc9000329f348
RBP: ffffc9000329f3d8 R08: ffffc9000329f347 R09: ffffc9000329f320
R10: dffffc0000000000 R11: fffff52000653e69 R12: dffffc0000000000
R13: 0000000000000000 R14: 0000000000040dc0 R15: 0000000000000011
FS: 00007fac38fbb6c0(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3171223ff8 CR3: 000000002a678000 CR4: 00000000003506f0
Call Trace:
<TASK>
kmalloc_order+0x40/0x150 mm/slab_common.c:986
kmalloc_order_trace+0x14/0xf0 mm/slab_common.c:1002
kmalloc include/linux/slab.h:612 [inline]
kzalloc include/linux/slab.h:738 [inline]
create_strip_zones+0xa25/0x1f60 drivers/md/raid0.c:149
raid0_run+0x17e/0x1160 drivers/md/raid0.c:406
md_run+0xf11/0x22f0 drivers/md/md.c:6007
do_md_run+0x30/0x400 drivers/md/md.c:6132
md_ioctl+0x202a/0x26b0 drivers/md/md.c:7786
blkdev_ioctl+0x33b/0x700 block/ioctl.c:604
block_ioctl+0xac/0xf0 block/fops.c:496
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fac3ad61799
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fac38fbb028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fac3afdafa0 RCX: 00007fac3ad61799
RDX: 0000200002000005 RSI: 00000000400c0930 RDI: 0000000000000004
RBP: 00007fac3adf7bd9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fac3afdb038 R14: 00007fac3afdafa0 R15: 00007ffe7fdcd1b8
</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