From: Andrew Morton <akpm@linux-foundation.org>
To: Lillian Berry <lillian@star-ark.net>
Cc: linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] init/main.c: add warning when file specified in rdinit is inaccessible
Date: Sun, 6 Jul 2025 13:13:24 -0700 [thread overview]
Message-ID: <20250706131324.613340ff7e99231c383409f5@linux-foundation.org> (raw)
In-Reply-To: <20250706185142.1294007-1-lillian@star-ark.net>
On Sun, 6 Jul 2025 18:51:41 +0000 Lillian Berry <lillian@star-ark.net> wrote:
> Avoid silently ignoring the initramfs when the file specified in rdinit
> is not usable. This prints an error that clearly explains the issue
> (file was not found, vs initramfs was not found).
>
> Signed-off-by: Lillian Berry <lillian@star-ark.net>
> ---
> init/main.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/init/main.c b/init/main.c
> index 225a58279acd..f391f62864a6 100644
> --- a/init/main.c
> +++ b/init/main.c
> @@ -1593,6 +1593,8 @@ static noinline void __init kernel_init_freeable(void)
> * the work
> */
> if (init_eaccess(ramdisk_execute_command) != 0) {
> + pr_warn("WARNING: rdinit=%s is inaccessible or not existing, ignoring\n",
"is inaccessible or does not exist", please.
Is the "WARNING: " needed? It's pr_warn(), which implies that it's a warning.
It would be good to display the errno itself. This way people can just
look up the numeric value so there's no need for this code to expand it
into text.
Perhaps the kernel should have an strerror() for this sort of thing,
but I don't think we do. The required table is buried down in
net/9p/error.c, for some reason!
next prev parent reply other threads:[~2025-07-06 20:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-06 18:51 Lillian Berry
2025-07-06 20:13 ` Andrew Morton [this message]
2025-07-06 20:29 ` Lillian Berry
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=20250706131324.613340ff7e99231c383409f5@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=lillian@star-ark.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®