mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thorsten Blum <thorsten.blum@linux.dev>
To: David Laight <david.laight.linux@gmail.com>
Cc: Borislav Petkov <bp@alien8.de>, Thomas Gleixner <tglx@kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Changyuan Lyu <changyuanl@google.com>,
	Alexander Graf <graf@amazon.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Mike Rapoport (Microsoft)" <rppt@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] x86/boot: Replace simple_strtoull in parse_gb_huge_pages
Date: Mon, 2 Mar 2026 12:12:02 +0100	[thread overview]
Message-ID: <01CBB333-424E-4A43-B7F7-B540C35BF1EA@linux.dev> (raw)
In-Reply-To: <20260301183012.3a12ea7f@pumpkin>

On 1. Mar 2026, at 19:30, David Laight wrote:
> On Sun, 1 Mar 2026 11:44:54 +0100 Borislav Petkov wrote:
>> On Mon, Feb 02, 2026 at 06:32:20PM +0100, Thorsten Blum wrote:
>>> Replace simple_strtoull() with the recommended boot_kstrtoul() for
>>> parsing the 'hugepages=' boot parameter. Unlike simple_strtoull(), which
>>> returns an unsigned long long, boot_kstrtoul() converts the string
>>> directly to an unsigned long and avoids implicit casting.  
>> 
>> "The respective kstrtol(), kstrtoll(), kstrtoul(), and kstrtoull() functions
>> tend to be the correct replacements, though note that those require the string
>> to be NUL or newline terminated."
>> 
>> Where are we making sure of that?
>> 
>>> Check the return value of boot_kstrtoul() and warn about invalid values.
>>> 
>>> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
>>> ---
>>> arch/x86/boot/compressed/kaslr.c | 3 ++-
>>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>> [...]
>> 
>> Make that
>> 
>> warn("Failed to parse hugepages= boot parameter\n");
> 
> I'd suggest including the 'val' that failed to parse.

warn() isn't variadic and cannot print format arguments. We could add
another helper (e.g., warn_param()) or use error_putstr() manually, but
I'm not sure it's worth it for this case. Any other thoughts on this?

Thanks,
Thorsten


      reply	other threads:[~2026-03-02 11:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-02 17:32 Thorsten Blum
2026-03-01 10:44 ` Borislav Petkov
2026-03-01 12:13   ` Thorsten Blum
2026-03-01 18:30   ` David Laight
2026-03-02 11:12     ` Thorsten Blum [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=01CBB333-424E-4A43-B7F7-B540C35BF1EA@linux.dev \
    --to=thorsten.blum@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=changyuanl@google.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=david.laight.linux@gmail.com \
    --cc=graf@amazon.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rppt@kernel.org \
    --cc=tglx@kernel.org \
    --cc=x86@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

all inboxes | Powered by JetHome®