qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Alexander Graf <agraf@suse.de>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
	Jens Freimann <jfrei@linux.vnet.ibm.com>,
	Heinz Graalfs <graalfs@linux.vnet.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Einar Lueck <elelueck@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 1/3] s390: Fix empty kernel command line
Date: Tue, 11 Dec 2012 12:15:03 +0100	[thread overview]
Message-ID: <50C715B7.4060006@de.ibm.com> (raw)
In-Reply-To: <014C9A5F-A2A2-47C8-AEF3-D17F56208090@suse.de>

On 11/12/12 11:34, Alexander Graf wrote:
> 
> On 07.12.2012, at 14:55, Jens Freimann wrote:
> 
>> From: Christian Borntraeger <borntraeger@de.ibm.com>
>>
>> Since commit 967c0da73a7b0da186baba6632301d83644a570c
>>    vl.c: Avoid segfault when started with no arguments
>>
>> the user can specify a kernel without a command line. Lets not
>> overwrite the default command line with \0 in that case.
>>
>> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
>> Signed-off-by: Jens Freimann <jfrei@linux.vnet.ibm.com>
>> ---
>> hw/s390-virtio.c |    2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/hw/s390-virtio.c b/hw/s390-virtio.c
>> index ca1bb09..d77871a 100644
>> --- a/hw/s390-virtio.c
>> +++ b/hw/s390-virtio.c
>> @@ -290,7 +290,7 @@ static void s390_init(QEMUMachineInitArgs *args)
>>         stq_p(rom_ptr(INITRD_PARM_SIZE), initrd_size);
>>     }
>>
>> -    if (rom_ptr(KERN_PARM_AREA)) {
>> +    if (rom_ptr(KERN_PARM_AREA) && strlen(kernel_cmdline)) {
> 
> why strlen()? If no -append option was passed, kernel_cmdline should be NULL. If -append "" was passed, the user wants to command line to be overwritten with "\0".

Nope. kernel_cmdline is always a valid pointer.

vl.c:

[..]
    if (!kernel_cmdline) {
        kernel_cmdline = "";
    }

[..]

  reply	other threads:[~2012-12-11 11:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-07 13:55 [Qemu-devel] [PATCH 0/3] s390: ipl device and cpu reset handler Jens Freimann
2012-12-07 13:55 ` [Qemu-devel] [PATCH 1/3] s390: Fix empty kernel command line Jens Freimann
2012-12-11 10:34   ` Alexander Graf
2012-12-11 11:15     ` Christian Borntraeger [this message]
2012-12-11 11:19       ` Alexander Graf
2012-12-11 11:26         ` Christian Borntraeger
2012-12-07 13:55 ` [Qemu-devel] [PATCH 2/3] s390: Move IPL code into a separate device Jens Freimann
2012-12-07 15:14   ` [Qemu-devel] [RFC/PATCH 0/2] ipl device followup Christian Borntraeger
2012-12-07 15:14     ` [Qemu-devel] [RFC/PATCH 1/2] s390: Add bootmap parsing to ipl device Christian Borntraeger
2012-12-07 15:14     ` [Qemu-devel] [RFC/PATCH 2/2] s390: enable ipl device for virtio-ccw Christian Borntraeger
2012-12-11 10:36     ` [Qemu-devel] [RFC/PATCH 0/2] ipl device followup Alexander Graf
2012-12-11 10:38   ` [Qemu-devel] [PATCH 2/3] s390: Move IPL code into a separate device Alexander Graf
2012-12-07 13:55 ` [Qemu-devel] [PATCH 3/3] s390: add cpu reset handler Jens Freimann
2012-12-07 19:07   ` Andreas Färber
2012-12-08 17:32     ` Jens Freimann

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=50C715B7.4060006@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=agraf@suse.de \
    --cc=cornelia.huck@de.ibm.com \
    --cc=elelueck@linux.vnet.ibm.com \
    --cc=graalfs@linux.vnet.ibm.com \
    --cc=jfrei@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).