From: Simon Horman <horms@verge.net.au>
To: kexec@lists.infradead.org
Subject: [PATCH v3 0/5] s390: add support for extended cmdline length
Date: Fri, 14 Jan 2022 16:05:06 +0100 [thread overview]
Message-ID: <20220114150506.GI16732@vergenet.net> (raw)
In-Reply-To: <20211216114356.605851-1-svens@linux.ibm.com>
On Thu, Dec 16, 2021 at 12:43:51PM +0100, Sven Schnelle wrote:
> Hi,
>
> this patchset adds support for extended command line lengths on s390.
> The former limit of 896 has been too short in a some configurations. The
> linux kernel now provides an additional field in the parameter area
> which contains the maximum allowed command line length. In older kernels
> this field is zero. In that case the old limit of 896 bytes is used.
> This was introduced with 5ecb2da660ab ("s390: support command lines
> longer than 896 bytes") in linux.
>
> And while at it, also add the --reuse-cmdline option and use
> KEXEC_ALL_OPTIONS.
>
> Changes in v3:
> - handle short reads and interruptions in slurp_proc_file()
>
> Changes in v2:
>
> - add slurp_proc_file() to read proc files without knowing the size upfront
> - move command_line string from global to function scope
Thanks, applied.
prev parent reply other threads:[~2022-01-14 15:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 11:43 [PATCH v3 0/5] s390: add support for extended cmdline length Sven Schnelle
2021-12-16 11:43 ` [PATCH v3 1/5] s390: add variable command line size Sven Schnelle
2021-12-16 11:43 ` [PATCH v3 2/5] s390: use KEXEC_ALL_OPTIONS Sven Schnelle
2021-12-16 11:43 ` [PATCH v3 3/5] add slurp_proc_file() Sven Schnelle
2021-12-16 11:43 ` [PATCH v3 4/5] use slurp_proc_file() in get_command_line() Sven Schnelle
2021-12-16 11:43 ` [PATCH v3 5/5] s390: add support for --reuse-cmdline Sven Schnelle
2022-01-14 15:05 ` Simon Horman [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=20220114150506.GI16732@vergenet.net \
--to=horms@verge.net.au \
--cc=kexec@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.