From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org, mike.kravetz@oracle.com, guro@fb.com,
chenwandun@huawei.com
Subject: + mm-hugetlb-suppress-wrong-warning-info-when-alloc-gigantic-page.patch added to -mm tree
Date: Fri, 19 Feb 2021 15:19:23 -0800 [thread overview]
Message-ID: <20210219231923.81_M1%akpm@linux-foundation.org> (raw)
The patch titled
Subject: mm/hugetlb: suppress wrong warning info when alloc gigantic page
has been added to the -mm tree. Its filename is
mm-hugetlb-suppress-wrong-warning-info-when-alloc-gigantic-page.patch
This patch should soon appear at
https://ozlabs.org/~akpm/mmots/broken-out/mm-hugetlb-suppress-wrong-warning-info-when-alloc-gigantic-page.patch
and later at
https://ozlabs.org/~akpm/mmotm/broken-out/mm-hugetlb-suppress-wrong-warning-info-when-alloc-gigantic-page.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Chen Wandun <chenwandun@huawei.com>
Subject: mm/hugetlb: suppress wrong warning info when alloc gigantic page
If hugetlb_cma is enabled, it will skip boot time allocation when
allocating gigantic page, that doesn't means allocation failure, so
suppress this warning info.
Link: https://lkml.kernel.org/r/20210219123909.13130-1-chenwandun@huawei.com
Fixes: cf11e85fc08c ("mm: hugetlb: optionally allocate gigantic hugepages using cma")
Signed-off-by: Chen Wandun <chenwandun@huawei.com>
Reviewed-by: Mike Kravetz <mike.kravetz@oracle.com>
Cc: Roman Gushchin <guro@fb.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/hugetlb.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/mm/hugetlb.c~mm-hugetlb-suppress-wrong-warning-info-when-alloc-gigantic-page
+++ a/mm/hugetlb.c
@@ -2529,7 +2529,7 @@ static void __init hugetlb_hstate_alloc_
if (hstate_is_gigantic(h)) {
if (hugetlb_cma_size) {
pr_warn_once("HugeTLB: hugetlb_cma is enabled, skip boot time allocation\n");
- break;
+ goto free;
}
if (!alloc_bootmem_huge_page(h))
break;
@@ -2547,7 +2547,7 @@ static void __init hugetlb_hstate_alloc_
h->max_huge_pages, buf, i);
h->max_huge_pages = i;
}
-
+free:
kfree(node_alloc_noretry);
}
_
Patches currently in -mm which might be from chenwandun@huawei.com are
mm-hugetlb-suppress-wrong-warning-info-when-alloc-gigantic-page.patch
next reply other threads:[~2021-02-19 23:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 23:19 akpm [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-02-19 18:37 + mm-hugetlb-suppress-wrong-warning-info-when-alloc-gigantic-page.patch added to -mm tree akpm
2021-02-19 19:47 ` Roman Gushchin
2021-02-19 20:04 ` Mike Kravetz
2021-02-19 20:11 ` Roman Gushchin
2021-02-19 21:19 ` Mike Kravetz
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=20210219231923.81_M1%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=chenwandun@huawei.com \
--cc=guro@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=mm-commits@vger.kernel.org \
/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