From: Huacai Chen <chenhuacai@kernel.org>
To: Huacai Chen <chenhuacai@loongson.cn>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH V3] init: Handle bootloader identifier in kernel parameters
Date: Sun, 10 Aug 2025 22:34:10 +0800 [thread overview]
Message-ID: <CAAhV-H4TToP7AY8yMUjikTLChMpMQMB1=HRaMDS7Ern5nf92Fg@mail.gmail.com> (raw)
In-Reply-To: <20250721101343.3283480-1-chenhuacai@loongson.cn>
Hi, Andrew,
Can you take this patch to linux-mm (seems the best tree for it)?
Huacai
On Mon, Jul 21, 2025 at 6:14 PM Huacai Chen <chenhuacai@loongson.cn> wrote:
>
> BootLoader (Grub, LILO, etc) may pass an identifier such as "BOOT_IMAGE=
> /boot/vmlinuz-x.y.z" to kernel parameters. But these identifiers are not
> recognized by the kernel itself so will be passed to user space. However
> user space init program also doesn't recognized it.
>
> KEXEC/KDUMP (kexec-tools) may also pass an identifier such as "kexec" on
> some architectures.
>
> We cannot change BootLoader's behavior, because this behavior exists for
> many years, and there are already user space programs search BOOT_IMAGE=
> in /proc/cmdline to obtain the kernel image locations:
>
> https://github.com/linuxdeepin/deepin-ab-recovery/blob/master/util.go
> (search getBootOptions)
> https://github.com/linuxdeepin/deepin-ab-recovery/blob/master/main.go
> (search getKernelReleaseWithBootOption)
>
> So the the best way is handle (ignore) it by the kernel itself, which
> can avoid such boot warnings (if we use something like init=/bin/bash,
> bootloader identifier can even cause a crash):
>
> Kernel command line: BOOT_IMAGE=(hd0,1)/vmlinuz-6.x root=/dev/sda3 ro console=tty
> Unknown kernel command line parameters "BOOT_IMAGE=(hd0,1)/vmlinuz-6.x", will be passed to user space.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
> ---
> V2: Update comments and commit messages.
> V3: Document bootloader identifiers.
>
> init/main.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/init/main.c b/init/main.c
> index 225a58279acd..b25e7da5347a 100644
> --- a/init/main.c
> +++ b/init/main.c
> @@ -545,6 +545,12 @@ static int __init unknown_bootoption(char *param, char *val,
> const char *unused, void *arg)
> {
> size_t len = strlen(param);
> + /*
> + * Well-known bootloader identifiers:
> + * 1. LILO/Grub pass "BOOT_IMAGE=...";
> + * 2. kexec/kdump (kexec-tools) pass "kexec".
> + */
> + const char *bootloader[] = { "BOOT_IMAGE=", "kexec", NULL };
>
> /* Handle params aliased to sysctls */
> if (sysctl_is_alias(param))
> @@ -552,6 +558,12 @@ static int __init unknown_bootoption(char *param, char *val,
>
> repair_env_string(param, val);
>
> + /* Handle bootloader identifier */
> + for (int i = 0; bootloader[i]; i++) {
> + if (!strncmp(param, bootloader[i], strlen(bootloader[i])))
> + return 0;
> + }
> +
> /* Handle obsolete-style parameters */
> if (obsolete_checksetup(param))
> return 0;
> --
> 2.47.3
>
next prev parent reply other threads:[~2025-08-10 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 10:13 Huacai Chen
2025-08-10 14:34 ` Huacai Chen [this message]
2025-08-12 1:56 ` Andrew Morton
2025-08-15 8:50 ` Huacai Chen
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='CAAhV-H4TToP7AY8yMUjikTLChMpMQMB1=HRaMDS7Ern5nf92Fg@mail.gmail.com' \
--to=chenhuacai@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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