linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Yu Kuai" <yukuai@fnnas.com>
To: "Gregory Price" <gourry@gourry.net>, <song@kernel.org>,
	 <linan122@huawei.com>, <yukuai@fnnas.com>
Cc: <linux-raid@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	 <linux-mm@kvack.org>,
	 <syzbot+924649752adf0d3ac9dd@syzkaller.appspotmail.com>,
	 <akpm@linux-foundation.org>
Subject: Re: [PATCH] md/raid0: use kvzalloc/kvfree for strip_zone and devlist allocations
Date: Fri, 20 Mar 2026 12:08:41 +0800	[thread overview]
Message-ID: <d15b9cf0-94cc-4fd1-a702-e3e34f967f6b@fnnas.com> (raw)
In-Reply-To: <20260308234202.3118119-1-gourry@gourry.net>

在 2026/3/9 7:42, Gregory Price 写道:

> syzbot reported a WARNING at mm/page_alloc.c:__alloc_frozen_pages_noprof()
> triggered by create_strip_zones() in the RAID0 driver.
>
> When raid_disks is large, the allocation size exceeds MAX_PAGE_ORDER (4MB
> on x86), causing WARN_ON_ONCE_GFP(order > MAX_PAGE_ORDER).
>
> Convert the strip_zone and devlist allocations from kzalloc/kzalloc_objs to
> kvzalloc/kvzalloc_objs, which first attempts a contiguous allocation with
> __GFP_NOWARN and then falls back to vmalloc for large sizes. Convert the
> corresponding kfree calls to kvfree.
>
> Both arrays are pure metadata lookup tables (arrays of pointers and zone
> descriptors) accessed only via indexing, so they do not require physically
> contiguous memory.
>
> Reported-by:syzbot+924649752adf0d3ac9dd@syzkaller.appspotmail.com
> Signed-off-by: Gregory Price<gourry@gourry.net>
> ---
>   drivers/md/raid0.c | 18 +++++++++---------
>   1 file changed, 9 insertions(+), 9 deletions(-)

Reviewed-by: Yu Kuai <yukuai@fnnas.com>

-- 
Thansk,
Kuai


  reply	other threads:[~2026-03-20  4:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-08 17:02 [syzbot] [mm?] WARNING in create_strip_zones syzbot
2026-03-08 23:42 ` [PATCH] md/raid0: use kvzalloc/kvfree for strip_zone and devlist allocations Gregory Price
2026-03-20  4:08   ` Yu Kuai [this message]
2026-03-21  6:29   ` Li Nan
2026-04-07  5:06   ` Yu Kuai
2026-04-07 16:04     ` Gregory Price

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=d15b9cf0-94cc-4fd1-a702-e3e34f967f6b@fnnas.com \
    --to=yukuai@fnnas.com \
    --cc=akpm@linux-foundation.org \
    --cc=gourry@gourry.net \
    --cc=linan122@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=song@kernel.org \
    --cc=syzbot+924649752adf0d3ac9dd@syzkaller.appspotmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox