qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Marc Hartmayer" <mhartmay@linux.ibm.com>,
	qemu-devel@nongnu.org
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
	qemu-s390x <qemu-s390x@nongnu.org>,
	Cornelia Huck <cohuck@redhat.com>,
	Sven Schnelle <svens@linux.ibm.com>
Subject: Re: [PATCH] s390x/ipl: check kernel command line size
Date: Tue, 12 Oct 2021 08:53:00 +0200	[thread overview]
Message-ID: <3f5dbbea-aeb7-b0a8-2eed-209c9a0a4ba6@redhat.com> (raw)
In-Reply-To: <016d8001-24aa-b4e3-ce1a-92f275d4bec5@redhat.com>

On 11/10/2021 20.08, Philippe Mathieu-Daudé wrote:
> On 10/11/21 15:38, Thomas Huth wrote:
>> On 06/10/2021 11.26, Marc Hartmayer wrote:
>>> Check if the provided kernel command line exceeds the maximum size of
>>> the s390x
>>> Linux kernel command line size, which is 896 bytes.
>>>
>>> Reported-by: Sven Schnelle <svens@linux.ibm.com>
>>> Signed-off-by: Marc Hartmayer <mhartmay@linux.ibm.com>
>>> ---
>>>    hw/s390x/ipl.c | 12 +++++++++++-
>>>    1 file changed, 11 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/hw/s390x/ipl.c b/hw/s390x/ipl.c
>>> index 1821c6faeef3..a58ea58cc736 100644
>>> --- a/hw/s390x/ipl.c
>>> +++ b/hw/s390x/ipl.c
>>> @@ -38,6 +38,7 @@
>>>    #define KERN_IMAGE_START                0x010000UL
>>>    #define LINUX_MAGIC_ADDR                0x010008UL
>>>    #define KERN_PARM_AREA                  0x010480UL
>>> +#define KERN_PARM_AREA_SIZE             0x000380UL
>>>    #define INITRD_START                    0x800000UL
>>>    #define INITRD_PARM_START               0x010408UL
>>>    #define PARMFILE_START                  0x001000UL
>>> @@ -190,10 +191,19 @@ static void s390_ipl_realize(DeviceState *dev,
>>> Error **errp)
>>>             * loader) and it won't work. For this case we force it to
>>> 0x10000, too.
>>>             */
>>>            if (pentry == KERN_IMAGE_START || pentry == 0x800) {
>>> -            char *parm_area = rom_ptr(KERN_PARM_AREA,
>>> strlen(ipl->cmdline) + 1);
>>> +            size_t cmdline_size = strlen(ipl->cmdline) + 1;
>>> +            char *parm_area = rom_ptr(KERN_PARM_AREA, cmdline_size);
>>> +
>>>                ipl->start_addr = KERN_IMAGE_START;
>>>                /* Overwrite parameters in the kernel image, which are
>>> "rom" */
>>>                if (parm_area) {
>>> +                if (cmdline_size > KERN_PARM_AREA_SIZE) {
>>> +                    error_setg(errp,
>>> +                               "kernel command line exceeds maximum
>>> size: %lu > %lu",
>>
>> I think the first %lu should be %zd instead?
> 
> %zu ;)

All right, queued with %zu on my s390x-next branch:

  https://gitlab.com/thuth/qemu/-/commits/s390x-next/

  Thomas



      reply	other threads:[~2021-10-12  6:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-06  9:26 [PATCH] s390x/ipl: check kernel command line size Marc Hartmayer
2021-10-06 17:34 ` Christian Borntraeger
2021-10-11 13:38 ` Thomas Huth
2021-10-11 14:44   ` Marc Hartmayer
2021-10-11 18:08   ` Philippe Mathieu-Daudé
2021-10-12  6:53     ` Thomas Huth [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=3f5dbbea-aeb7-b0a8-2eed-209c9a0a4ba6@redhat.com \
    --to=thuth@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=mhartmay@linux.ibm.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=svens@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).