qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: qemu-devel@nongnu.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [Qemu-devel] [PATCH] pc_init: Fail on bad kernel
Date: Fri, 09 Sep 2011 12:57:57 -0500	[thread overview]
Message-ID: <4E6A53A5.7020904@us.ibm.com> (raw)
In-Reply-To: <1315078543-28522-1-git-send-email-levinsasha928@gmail.com>

On 09/03/2011 02:35 PM, Sasha Levin wrote:
> When providing QEMU with a bad '-kernel' parameter, such as a file which
> is not really a kernel, QEMU will attempt to allocate a huge amount of
> memory and fail either with "Failed to allocate memory: Cannot allocate
> memory" or a GLib error: "GLib-ERROR **: gmem.c:170: failed to allocate
> 18446744073709529965 bytes"
>
> This patch handles the case where the magic sig wasn't located in the
> provided kernel, and loading it as multiboot failed as well.
>
> Cc: Anthony Liguori<aliguori@us.ibm.com>
> Signed-off-by: Sasha Levin<levinsasha928@gmail.com>
> ---
>   hw/pc.c |    8 +++++++-
>   1 files changed, 7 insertions(+), 1 deletions(-)
>
> diff --git a/hw/pc.c b/hw/pc.c
> index 6b3662e..428440b 100644
> --- a/hw/pc.c
> +++ b/hw/pc.c
> @@ -691,8 +691,14 @@ static void load_linux(void *fw_cfg,
>   	/* This looks like a multiboot kernel. If it is, let's stop
>   	   treating it like a Linux kernel. */
>           if (load_multiboot(fw_cfg, f, kernel_filename, initrd_filename,
> -                           kernel_cmdline, kernel_size, header))
> +                           kernel_cmdline, kernel_size, header)) {
>               return;
> +        } else {
> +            fprintf(stderr, "qemu: could not load kernel '%s': %s\n",
> +		    kernel_filename, strerror(errno));
> +	    exit(1);
> +        }
> +	

There's trailing whitespace on this line.

But I also don't think this is the right fix.  This change makes the 
line below unreachable.  There is still code in this path attempting to 
handle protocols < 2.00.  Admittedly, these would be ancient kernels 
that I doubt anyone would really use but the code is there to support it 
nonetheless.

I think a better fix would be to positively identify kernels that are 
older than this.

Perhaps hpa knows how we could positively identify a kernel that's older 
than protocol 200?

Regards,

Anthony Liguori

>   	protocol = 0;
>       }
>

  reply	other threads:[~2011-09-09 17:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-03 19:35 [Qemu-devel] [PATCH] pc_init: Fail on bad kernel Sasha Levin
2011-09-09 17:57 ` Anthony Liguori [this message]
2011-09-14  7:45 ` Sasha Levin
2011-09-14 12:54   ` Anthony Liguori

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=4E6A53A5.7020904@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=hpa@zytor.com \
    --cc=levinsasha928@gmail.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).