linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Jinjiang Tu <tujinjiang@huawei.com>,
	akpm@linux-foundation.org, alobakin@pm.me,
	mgorman@techsingularity.net, david@redhat.com
Cc: linux-mm@kvack.org, wangkefeng.wang@huawei.com, sunnanyong@huawei.com
Subject: Re: [PATCH] mm: fix NULL pointer dereference in alloc_pages_bulk_noprof
Date: Wed, 13 Nov 2024 15:11:10 +0100	[thread overview]
Message-ID: <fd941c4d-2c40-40d6-bfa2-dc76330d4fff@suse.cz> (raw)
In-Reply-To: <20241113083235.166798-1-tujinjiang@huawei.com>

On 11/13/24 09:32, Jinjiang Tu wrote:
> We triggered a NULL pointer dereference for ac.preferred_zoneref->zone
> in alloc_pages_bulk_noprof() when the task is migrated between cpusets.
> 
> When cpuset is enabled, in prepare_alloc_pages(), ac->nodemask may be
> &current->mems_allowed. when first_zones_zonelist() is called to find
> preferred_zoneref, the ac->nodemask may be modified concurrently if the
> task is migrated between different cpusets. Assuming we have 2 NUMA Node,
> when traversing Node1 in ac->zonelist, the nodemask is 2, and when
> traversing Node2 in ac->zonelist, the nodemask is 1. As a result, the
> ac->preferred_zoneref points to NULL zone.
> 
> In alloc_pages_bulk_noprof(), for_each_zone_zonelist_nodemask() finds a
> allowable zone and calls zonelist_node_idx(ac.preferred_zoneref), leading
> to NULL pointer dereference.
> 
> __alloc_pages_noprof() fixes this issue by checking NULL pointer in commit
> ea57485af8f4 ("mm, page_alloc: fix check for NULL preferred_zone") and
> commit df76cee6bbeb ("mm, page_alloc: remove redundant checks from alloc
> fastpath").
> 
> To fix it, check NULL pointer for preferred_zoneref->zone.
> 
> Fixes: 387ba26fb1cb ("mm/page_alloc: add a bulk page allocator")
> Signed-off-by: Jinjiang Tu <tujinjiang@huawei.com>

Reviewed-by: Vlastimil Babka <vbabka@suse.cz>

Thanks.

> ---
>  mm/page_alloc.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index c6c7bb3ea71b..4afe8bc06358 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -4592,7 +4592,8 @@ unsigned long alloc_pages_bulk_noprof(gfp_t gfp, int preferred_nid,
>  	gfp = alloc_gfp;
>  
>  	/* Find an allowed local zone that meets the low watermark. */
> -	for_each_zone_zonelist_nodemask(zone, z, ac.zonelist, ac.highest_zoneidx, ac.nodemask) {
> +	z = ac.preferred_zoneref;
> +	for_next_zone_zonelist_nodemask(zone, z, ac.highest_zoneidx, ac.nodemask) {
>  		unsigned long mark;
>  
>  		if (cpusets_enabled() && (alloc_flags & ALLOC_CPUSET) &&



      reply	other threads:[~2024-11-13 14:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-13  8:32 Jinjiang Tu
2024-11-13 14:11 ` Vlastimil Babka [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=fd941c4d-2c40-40d6-bfa2-dc76330d4fff@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=alobakin@pm.me \
    --cc=david@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=sunnanyong@huawei.com \
    --cc=tujinjiang@huawei.com \
    --cc=wangkefeng.wang@huawei.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