From: syzbot <syzbot+a32ff75e417c0f49a8e9@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
magiclinan@didiglobal.com, song@kernel.org,
syzkaller-bugs@googlegroups.com, xiao@kernel.org,
yukuai@fnnas.com, yukuai@fygo.io
Subject: Re: [syzbot] [raid?] WARNING in create_strip_zones (2)
Date: Fri, 04 Sep 2026 13:46:23 -0700 [thread overview]
Message-ID: <6a9b2e1f.a5e650b3.363816.0001.GAE@google.com> (raw)
In-Reply-To: <6a972e63.610165a0.2b3dfd.0001.GAE@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: bc35965f6940 Merge tag 'mm-hotfixes-stable-2026-09-03-17-4..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=12271215580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8c5c3949d762a91f
dashboard link: https://syzkaller.appspot.com/bug?extid=a32ff75e417c0f49a8e9
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=173f2b49580000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a32ff75e417c0f49a8e9@syzkaller.appspotmail.com
------------[ cut here ]------------
!(flags & __GFP_NOWARN)
WARNING: mm/slub.c:7013 at __kvmalloc_node_noprof+0x646/0x9b0 mm/slub.c:7013, CPU#3: syz-executor142/6020
Modules linked in:
CPU: 3 UID: 0 PID: 6020 Comm: syz-executor142 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:__kvmalloc_node_noprof+0x646/0x9b0 mm/slub.c:7013
Code: c1 e8 2e 07 ff ff 4d 85 f6 0f 85 b6 fd ff ff 48 81 fb ff ff ff 7f 0f 86 4d fd ff ff 41 81 e4 00 20 00 00 0f 85 9c fd ff ff 90 <0f> 0b 90 e9 93 fd ff ff 41 be 10 00 00 00 e9 88 fd ff ff be 42 01
RSP: 0018:ffffc900036bf948 EFLAGS: 00010246
RAX: 0000000000000001 RBX: 0000000200000000 RCX: 0000000200000000
RDX: 0000000000000000 RSI: ffffffff8c620f00 RDI: ffffffff8e6b6938
RBP: 00000000001fffff R08: 00000000000029c0 R09: 00000000ffffffff
R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000000
R13: 00000000000029c0 R14: 0000000000000000 R15: 00000000ffffffff
FS: 0000555559921400(0000) GS:ffff8880d5e60000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055bcaf223cc0 CR3: 0000000055943000 CR4: 0000000000352ef0
Call Trace:
<TASK>
create_strip_zones+0x57f/0x1fa0 drivers/md/raid0.c:150
raid0_run+0x341/0x410 drivers/md/raid0.c:424
md_run+0xc2f/0x2510 drivers/md/md.c:6779
do_md_run+0x36/0x660 drivers/md/md.c:6880
md_ioctl+0x27eb/0x36d0 drivers/md/md.c:8515
blkdev_ioctl+0x5ad/0x6f0 block/ioctl.c:798
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl fs/ioctl.c:583 [inline]
__x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x123/0x790 arch/x86/entry/syscall_64.c:84
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f76d13e162b
Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 00 00
RSP: 002b:00007ffc9fbd7ba0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f76d13e162b
RDX: 0000000000000000 RSI: 00000000400c0930 RDI: 0000000000000003
RBP: 0000000000000004 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f76d143a032
R13: 0000000000000002 R14: 00007f76d1464cc0 R15: 0000000000000002
</TASK>
---
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.
prev parent reply other threads:[~2026-09-04 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 19:58 [syzbot] [raid?] WARNING in create_strip_zones (2) syzbot
2026-09-04 20:46 ` syzbot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6a9b2e1f.a5e650b3.363816.0001.GAE@google.com \
--to=syzbot+a32ff75e417c0f49a8e9@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=magiclinan@didiglobal.com \
--cc=song@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xiao@kernel.org \
--cc=yukuai@fnnas.com \
--cc=yukuai@fygo.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.