From: David Laight <david.laight.linux@gmail.com>
To: Ilya Leoshkevich <iii@linux.ibm.com>
Cc: Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390: Warn if kernel command line contains non-printable EBCDIC characters
Date: Wed, 26 Aug 2026 14:51:29 +0100 [thread overview]
Message-ID: <20260826145129.204b6517@pumpkin> (raw)
In-Reply-To: <20260825150840.537653-1-iii@linux.ibm.com>
On Tue, 25 Aug 2026 17:08:08 +0200
Ilya Leoshkevich <iii@linux.ibm.com> wrote:
> Users may accidentally add multi-byte UTF-8 characters to zipl.conf
> parmline, for example, by copying snippets containing non-breaking
> spaces (\xC2\xA0) from web pages.
>
> The kernel will then interpret the entire command line as EBCDIC,
> making it unusable. Distinguish this situation from the legitimate
> EBCDIC conversion by looking for non-printable characters and issue
> a warning.
Would it be better to check for the entire line being printable ebcdic?
All of EBCDIC a-zA-Z0-9 have the 0x80 bit set and most of 0x20..0x7f
are invalid or control characters (or punctuation).
David
>
> Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
> ---
> arch/s390/boot/ipl_parm.c | 19 ++++++++++++++++++-
> 1 file changed, 18 insertions(+), 1 deletion(-)
>
> diff --git a/arch/s390/boot/ipl_parm.c b/arch/s390/boot/ipl_parm.c
> index 6bc950b92be76..71c0c26d56bba 100644
> --- a/arch/s390/boot/ipl_parm.c
> +++ b/arch/s390/boot/ipl_parm.c
> @@ -173,12 +173,29 @@ static inline int has_ebcdic_char(const char *str)
> return 0;
> }
>
> +static inline int has_nonprintable_char(const char *str)
> +{
> + int i;
> +
> + for (i = 0; str[i]; i++) {
> + unsigned char c = (unsigned char)str[i];
> +
> + /* isprint() is Latin-1, and we need ASCII here */
> + if (c < 0x20 || c > 0x7e)
> + return 1;
> + }
> + return 0;
> +}
> +
> void setup_boot_command_line(void)
> {
> parmarea.command_line[COMMAND_LINE_SIZE - 1] = 0;
> /* convert arch command line to ascii if necessary */
> - if (has_ebcdic_char(parmarea.command_line))
> + if (has_ebcdic_char(parmarea.command_line)) {
> EBCASC(parmarea.command_line, COMMAND_LINE_SIZE);
> + if (has_nonprintable_char(parmarea.command_line))
> + boot_warn("Kernel command line was treated as EBCDIC, but contains non-printable characters\n");
> + }
> /* copy arch command line */
> strscpy(early_command_line, strim(parmarea.command_line));
>
next prev parent reply other threads:[~2026-08-26 13:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 15:08 [PATCH] s390: Warn if kernel command line contains non-printable EBCDIC characters Ilya Leoshkevich
2026-08-25 15:20 ` sashiko-bot
2026-08-26 9:29 ` Heiko Carstens
2026-08-26 14:17 ` Ilya Leoshkevich
2026-08-26 13:51 ` David Laight [this message]
2026-08-26 14:08 ` Ilya Leoshkevich
2026-08-27 8:32 ` David Laight
2026-08-27 11:15 ` Ilya Leoshkevich
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=20260826145129.204b6517@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=agordeev@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.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