From: Thorsten Blum <thorsten.blum@linux.dev>
To: Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>
Cc: x86@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Thorsten Blum <thorsten.blum@linux.dev>
Subject: [PATCH 0/3] x86/vdso: improve vdso=/vdso32= boot parameter validation
Date: Sun, 7 Jun 2026 17:16:15 +0200 [thread overview]
Message-ID: <20260607151614.79567-5-thorsten.blum@linux.dev> (raw)
Replace the deprecated simple_strtoul() [1] with kstrtouint() when
parsing the vDSO boot parameters. This provides strict input validation,
rejects partial input, and warns when disabling vDSO for invalid values.
Adjust both warnings for consistency and update the documentation.
[1] https://www.kernel.org/doc/html/latest/process/deprecated.html#simple-strtol-simple-strtoll-simple-strtoul-simple-strtoull
Thorsten Blum (3):
x86/vdso: use kstrtouint() to validate vdso= boot parameter
x86/vdso: use kstrtouint() to validate vdso32= boot parameter
Documentation/arch/x86: remove obsolete vdso32=2 compatibility note
Documentation/admin-guide/kernel-parameters.txt | 5 +----
arch/x86/entry/vdso/vdso32-setup.c | 10 ++++------
arch/x86/entry/vdso/vma.c | 6 +++++-
3 files changed, 10 insertions(+), 11 deletions(-)
base-commit: 979c294509f9248fe1e7c358d582fb37dd5ca12d
next reply other threads:[~2026-06-07 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-07 15:16 Thorsten Blum [this message]
2026-06-07 15:16 ` [PATCH 1/3] x86/vdso: use kstrtouint() to validate vdso= boot parameter Thorsten Blum
2026-06-07 15:16 ` [PATCH 2/3] x86/vdso: use kstrtouint() to validate vdso32= " Thorsten Blum
2026-06-07 15:16 ` [PATCH 3/3] Documentation/arch/x86: remove obsolete vdso32=2 compatibility note Thorsten Blum
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=20260607151614.79567-5-thorsten.blum@linux.dev \
--to=thorsten.blum@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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