From: David Hildenbrand <david@redhat.com>
To: Peng Liu <liupeng256@huawei.com>,
mike.kravetz@oracle.com, akpm@linux-foundation.org,
yaozhenguo1@gmail.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 2/2] hugetlb: Fix return value of __setup handlers
Date: Fri, 1 Apr 2022 12:46:00 +0200 [thread overview]
Message-ID: <533f85f9-82e2-bfa7-3788-4b2a668daedf@redhat.com> (raw)
In-Reply-To: <20220401101232.2790280-3-liupeng256@huawei.com>
On 01.04.22 12:12, Peng Liu wrote:
> When __setup() return '0', using invalid option values causes the
> entire kernel boot option string to be reported as Unknown. Hugetlb
> calls __setup() and will return '0' when set invalid parameter
> string.
>
> The following phenomenon is observed:
> cmdline:
> hugepagesz=1Y hugepages=1
> dmesg:
> HugeTLB: unsupported hugepagesz=1Y
> HugeTLB: hugepages=1 does not follow a valid hugepagesz, ignoring
> Unknown kernel command line parameters "hugepagesz=1Y hugepages=1"
>
> Since hugetlb will print warn or error information before return for
> invalid parameter string, just use return '1' to avoid print again.
>
> Signed-off-by: Peng Liu <liupeng256@huawei.com>
> ---
> mm/hugetlb.c | 18 ++++++++----------
> 1 file changed, 8 insertions(+), 10 deletions(-)
>
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index 9cd746432ca9..6dde34c115c9 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -4131,12 +4131,11 @@ static int __init hugepages_setup(char *s)
> int count;
> unsigned long tmp;
> char *p = s;
> - int ret = 1;
Adding this in #1 to remove it in #2 is a bit sub-optimal IMHO.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-04-01 10:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 10:12 [PATCH v2 0/2] hugetlb: Fix confusing behavior Peng Liu
2022-04-01 10:12 ` [PATCH v2 1/2] hugetlb: Fix hugepages_setup when deal with pernode Peng Liu
2022-04-01 10:43 ` David Hildenbrand
2022-04-01 17:23 ` Mike Kravetz
2022-04-04 10:41 ` David Hildenbrand
2022-04-04 23:48 ` Mike Kravetz
2022-04-02 2:36 ` liupeng (DM)
2022-04-01 10:12 ` [PATCH v2 2/2] hugetlb: Fix return value of __setup handlers Peng Liu
2022-04-01 10:46 ` David Hildenbrand [this message]
2022-04-02 1:33 ` liupeng (DM)
2022-04-04 10:25 ` 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=533f85f9-82e2-bfa7-3788-4b2a668daedf@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liupeng256@huawei.com \
--cc=mike.kravetz@oracle.com \
--cc=stable@vger.kernel.org \
--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