From: Peng Liu <liupeng256@huawei.com>
To: <mike.kravetz@oracle.com>, <david@redhat.com>,
<akpm@linux-foundation.org>, <yaozhenguo1@gmail.com>,
<baolin.wang@linux.alibaba.com>, <songmuchun@bytedance.com>,
<liuyuntao10@huawei.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, <wangkefeng.wang@huawei.com>,
<dave@stgolabs.net>, <liupeng256@huawei.com>
Subject: [PATCH v4] hugetlb: Fix wrong use of nr_online_nodes
Date: Sat, 16 Apr 2022 10:35:26 +0000 [thread overview]
Message-ID: <20220416103526.3287348-1-liupeng256@huawei.com> (raw)
In-Reply-To: <20220413032915.251254-2-liupeng256@huawei.com>
Certain systems are designed to have sparse/discontiguous nodes. In
this case, nr_online_nodes can not be used to walk through numa node.
Also, a valid node may be greater than nr_online_nodes.
However, in hugetlb, it is assumed that nodes are contiguous. Recheck
all the places that use nr_online_nodes, and repair them one by one.
Suggested-by: David Hildenbrand <david@redhat.com>
Fixes: 4178158ef8ca ("hugetlbfs: fix issue of preallocation of gigantic pages can't work")
Fixes: b5389086ad7b ("hugetlbfs: extend the definition of hugepages parameter to support node allocation")
Fixes: e79ce9832316 ("hugetlbfs: fix a truncation issue in hugepages parameter")
Fixes: f9317f77a6e0 ("hugetlb: clean up potential spectre issue warnings")
Signed-off-by: Peng Liu <liupeng256@huawei.com>
---
v3->v4:
Make sure nid is valid before use node_online, and __alloc_bootmem_huge_page
is no need to check node_online, which is suggested by Kefeng.
mm/hugetlb.c | 12 +++++-------
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/mm/hugetlb.c b/mm/hugetlb.c
index b34f50156f7e..a386c5f94932 100644
--- a/mm/hugetlb.c
+++ b/mm/hugetlb.c
@@ -2979,8 +2979,6 @@ int __alloc_bootmem_huge_page(struct hstate *h, int nid)
struct huge_bootmem_page *m = NULL; /* initialize for clang */
int nr_nodes, node;
- if (nid != NUMA_NO_NODE && nid >= nr_online_nodes)
- return 0;
/* do node specific alloc */
if (nid != NUMA_NO_NODE) {
m = memblock_alloc_try_nid_raw(huge_page_size(h), huge_page_size(h),
@@ -3088,7 +3086,7 @@ static void __init hugetlb_hstate_alloc_pages(struct hstate *h)
}
/* do node specific alloc */
- for (i = 0; i < nr_online_nodes; i++) {
+ for_each_online_node(i) {
if (h->max_huge_pages_node[i] > 0) {
hugetlb_hstate_alloc_pages_onenode(h, i);
node_specific_alloc = true;
@@ -4049,7 +4047,7 @@ static int __init hugetlb_init(void)
default_hstate.max_huge_pages =
default_hstate_max_huge_pages;
- for (i = 0; i < nr_online_nodes; i++)
+ for_each_online_node(i)
default_hstate.max_huge_pages_node[i] =
default_hugepages_in_node[i];
}
@@ -4164,9 +4162,9 @@ static int __init hugepages_setup(char *s)
pr_warn("HugeTLB: architecture can't support node specific alloc, ignoring!\n");
return 0;
}
- if (tmp >= nr_online_nodes)
+ if (tmp >= MAX_NUMNODES || !node_online(tmp))
goto invalid;
- node = array_index_nospec(tmp, nr_online_nodes);
+ node = array_index_nospec(tmp, MAX_NUMNODES);
p += count + 1;
/* Parse hugepages */
if (sscanf(p, "%lu%n", &tmp, &count) != 1)
@@ -4294,7 +4292,7 @@ static int __init default_hugepagesz_setup(char *s)
*/
if (default_hstate_max_huge_pages) {
default_hstate.max_huge_pages = default_hstate_max_huge_pages;
- for (i = 0; i < nr_online_nodes; i++)
+ for_each_online_node(i)
default_hstate.max_huge_pages_node[i] =
default_hugepages_in_node[i];
if (hstate_is_gigantic(&default_hstate))
--
2.25.1
next prev parent reply other threads:[~2022-04-16 10:17 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 3:29 [PATCH v3 0/4] hugetlb: Fix some incorrect behavior Peng Liu
2022-04-13 3:29 ` [PATCH v3 1/4] hugetlb: Fix wrong use of nr_online_nodes Peng Liu
2022-04-13 4:42 ` Andrew Morton
2022-04-13 6:27 ` liupeng (DM)
2022-04-13 22:04 ` Andrew Morton
2022-04-14 1:28 ` liupeng (DM)
2022-04-13 6:29 ` Baolin Wang
2022-04-14 23:36 ` Mike Kravetz
2022-04-15 2:09 ` Davidlohr Bueso
2022-04-15 5:41 ` Kefeng Wang
2022-04-15 7:01 ` liupeng (DM)
2022-04-16 1:21 ` Kefeng Wang
2022-04-19 4:40 ` Andrew Morton
2022-04-19 8:54 ` Kefeng Wang
2022-04-16 10:35 ` Peng Liu [this message]
2022-04-18 5:53 ` [PATCH v4] " Kefeng Wang
2022-04-19 4:03 ` Andrew Morton
2022-04-19 14:07 ` Kefeng Wang
2022-04-20 6:17 ` liupeng (DM)
2022-04-29 9:32 ` David Hildenbrand
2022-04-13 3:29 ` [PATCH v3 2/4] hugetlb: Fix hugepages_setup when deal with pernode Peng Liu
2022-04-14 23:50 ` Mike Kravetz
2022-04-29 9:30 ` David Hildenbrand
2022-04-13 3:29 ` [PATCH v3 3/4] hugetlb: Fix return value of __setup handlers Peng Liu
2022-04-13 6:39 ` Baolin Wang
2022-04-13 7:55 ` Muchun Song
2022-04-13 8:16 ` liupeng (DM)
2022-04-13 8:21 ` Muchun Song
2022-04-13 8:45 ` Kefeng Wang
2022-04-13 9:01 ` Muchun Song
2022-04-15 0:01 ` Mike Kravetz
2022-04-15 2:24 ` Davidlohr Bueso
2022-04-29 3:02 ` [PATCH v4] mm: Using for_each_online_node and node_online instead of open coding Peng Liu
2022-04-29 9:29 ` David Hildenbrand
2022-04-29 11:44 ` Muchun Song
2022-04-13 3:29 ` [PATCH v3 4/4] hugetlb: Clean up hugetlb_cma_reserve Peng Liu
2022-04-13 5:50 ` Muchun Song
2022-04-13 6:41 ` Baolin Wang
2022-04-15 0:03 ` Mike Kravetz
2022-04-15 2:15 ` Davidlohr Bueso
2022-04-15 7:03 ` liupeng (DM)
2022-04-29 9:28 ` David Hildenbrand
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=20220416103526.3287348-1-liupeng256@huawei.com \
--to=liupeng256@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=dave@stgolabs.net \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuyuntao10@huawei.com \
--cc=mike.kravetz@oracle.com \
--cc=songmuchun@bytedance.com \
--cc=wangkefeng.wang@huawei.com \
--cc=yaozhenguo1@gmail.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