From: Sven Schnelle <svens@linux.ibm.com>
To: Philipp Rudo <prudo@redhat.com>
Cc: Simon Horman <horms@verge.net.au>,
kexec@lists.infradead.org,
Alexander Egorenkov <egorenar@linux.ibm.com>
Subject: Re: [PATCH 3/3] s390: add support for --reuse-cmdline
Date: Tue, 07 Dec 2021 17:12:42 +0100 [thread overview]
Message-ID: <yt9dsfv4pf5x.fsf@linux.ibm.com> (raw)
In-Reply-To: <20211207153404.4ff7f7fd@rhtmp> (Philipp Rudo's message of "Tue, 7 Dec 2021 15:34:04 +0100")
Hi Philipp,
Philipp Rudo <prudo@redhat.com> writes:
>> diff --git a/kexec/arch/s390/kexec-image.c b/kexec/arch/s390/kexec-image.c
>> index dbeb689b830a..310d967ea331 100644
>> --- a/kexec/arch/s390/kexec-image.c
>> +++ b/kexec/arch/s390/kexec-image.c
>> @@ -72,6 +72,10 @@ int image_s390_load_file(int argc, char **argv, struct kexec_info *info)
>> case OPT_RAMDISK:
>> ramdisk = optarg;
>> break;
>> + case OPT_REUSE_CMDLINE:
>> + free(command_line);
>> + command_line = get_command_line();
>
> get_command_line reads a maximum of 2048 bytes from /prc/cmdline. With
> the configurable size on s390 defaulting to 4096 bytes this will
> ultimately cause problems. So you need to make get_command_line more
> flexible first.
Thanks for pointing this out, i wasn't aware of that limitation. So we
likely want to change that to some dynamic allocation.
Sven
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2021-12-07 16:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 7:13 [PATCH 0/3] s390: add support for extended cmdline length Sven Schnelle
2021-11-22 7:13 ` [PATCH 1/3] s390: add variable command line size Sven Schnelle
2021-12-07 14:29 ` Philipp Rudo
2021-12-07 16:06 ` Sven Schnelle
2021-11-22 7:14 ` [PATCH 2/3] s390: use KEXEC_ALL_OPTIONS Sven Schnelle
2021-11-22 7:14 ` [PATCH 3/3] s390: add support for --reuse-cmdline Sven Schnelle
2021-12-07 14:34 ` Philipp Rudo
2021-12-07 16:12 ` Sven Schnelle [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=yt9dsfv4pf5x.fsf@linux.ibm.com \
--to=svens@linux.ibm.com \
--cc=egorenar@linux.ibm.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=prudo@redhat.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