From: Heiko Carstens <hca@linux.ibm.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Doug Anderson" <dianders@chromium.org>,
"Randy Dunlap" <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org, "Andrew Chant" <achant@google.com>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Brian Gerst" <brgerst@gmail.com>,
"Christian Brauner" <brauner@kernel.org>,
"Francesco Valla" <francesco@valla.it>,
"Guo Weikang" <guoweikang.kernel@gmail.com>,
"Huacai Chen" <chenhuacai@kernel.org>,
"Jan Hendrik Farr" <kernel@jfarr.cc>,
"Jeff Xu" <jeffxu@chromium.org>, "Kees Cook" <kees@kernel.org>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Michal Koutný" <mkoutny@suse.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Mike Rapoport (Microsoft)" <rppt@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Shakeel Butt" <shakeel.butt@linux.dev>,
"Tejun Heo" <tj@kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Uladzislau Rezki (Sony)" <urezki@gmail.com>,
"Sven Schnelle" <svens@linux.ibm.com>,
linux-s390 <linux-s390@vger.kernel.org>
Subject: Re: [PATCH] init/main.c: Wrap long kernel cmdline when printing to logs
Date: Tue, 21 Oct 2025 15:16:33 +0200 [thread overview]
Message-ID: <20251021131633.26700Dd6-hca@linux.ibm.com> (raw)
In-Reply-To: <CAMuHMdWGb0jVt9ziBtWdHWC9omPAFMHVPBHDpv0F1XzvR0THpg@mail.gmail.com>
On Tue, Oct 21, 2025 at 09:05:48AM +0200, Geert Uytterhoeven wrote:
> On Mon, 20 Oct 2025 at 18:04, Doug Anderson <dianders@chromium.org> wrote:
> > On Mon, Oct 20, 2025 at 8:42 AM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > > On Mon, 20 Oct 2025 at 17:33, Doug Anderson <dianders@chromium.org> wrote:
> > > > Printing the command line to the kernel log buffer is one of the very
> > > > rare cases where:
> > > > * There's a legitimate reason to print a (potentially) very long
> > > > string to the kernel buffer.
> > >
> > > arch/s390/Kconfig:
> > >
> > > config COMMAND_LINE_SIZE
> > > int "Maximum size of kernel command line"
> > > default 4096
> > > range 896 1048576
> > >
> > > Yummy...
> >
> > Wow, what are they expecting to stuff in there? An encoded initramfs
> > or something? I kinda feel like the 1MB number isn't something anyone
> > expects but is a number picked to effectively be "unlimited".
>
> Dunno, commit 622021cd6c560ce7 ("s390: make command line configurable")
> lacks the "why" part.
That was just a follow-on patch of commit 5ecb2da660ab ("s390: support command
lines longer than 896 bytes") which solved the real problem with a too short
maximum command line size back then. In order to never have to deal with this
sort of problem again it was made configurable.
But I doubt that anybody will change the default ever.
next prev parent reply other threads:[~2025-10-21 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251019100605.1.I095f1e2c6c27f9f4de0b4841f725f356c643a13f@changeid>
[not found] ` <2d514d61-121d-44fc-aec7-637dd0920de8@infradead.org>
[not found] ` <CAD=FV=VNyt1zG_8pS64wgV8VkZWiWJymnZ-XCfkrfaAhhFSKcA@mail.gmail.com>
[not found] ` <CAMuHMdVT-_UVAO=1jvTPEjKO0zy7H1rUrQz1ubMfHivF4HWJNA@mail.gmail.com>
[not found] ` <CAD=FV=WeXOj_hyA=V9hMLHOJ_m9ui5mP6cRv2DpjXnR62_nd2w@mail.gmail.com>
2025-10-21 7:05 ` [PATCH] init/main.c: Wrap long kernel cmdline when printing to logs Geert Uytterhoeven
2025-10-21 13:16 ` Heiko Carstens [this message]
2025-10-21 16:07 ` Doug Anderson
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=20251021131633.26700Dd6-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=achant@google.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=brauner@kernel.org \
--cc=brgerst@gmail.com \
--cc=chenhuacai@kernel.org \
--cc=dianders@chromium.org \
--cc=francesco@valla.it \
--cc=geert@linux-m68k.org \
--cc=guoweikang.kernel@gmail.com \
--cc=jeffxu@chromium.org \
--cc=kees@kernel.org \
--cc=kernel@jfarr.cc \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mkoutny@suse.com \
--cc=nathan@kernel.org \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=svens@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=thomas.weissschuh@linutronix.de \
--cc=tj@kernel.org \
--cc=urezki@gmail.com \
/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