[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YlaCA6kqjN5nYNSH@FVFYT0MHHV2J.usts.net>
Date: Wed, 13 Apr 2022 15:55:47 +0800
From: Muchun Song <songmuchun@...edance.com>
To: Peng Liu <liupeng256@...wei.com>
Cc: mike.kravetz@...cle.com, david@...hat.com,
akpm@...ux-foundation.org, yaozhenguo1@...il.com,
baolin.wang@...ux.alibaba.com, liuyuntao10@...wei.com,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 3/4] hugetlb: Fix return value of __setup handlers
On Wed, Apr 13, 2022 at 03:29:14AM +0000, 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 warning/error information before return for
> invalid parameter string, just use return '1' to avoid print again.
>
Can't return -EINVAL? It is weird to return 1 on failure.
Thanks.
Powered by blists - more mailing lists