qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] qcow2: Fix segfault on zero-length write
Date: Tue, 15 Jan 2013 09:17:01 +0100	[thread overview]
Message-ID: <20130115081701.GA21625@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1358181091-3857-1-git-send-email-kwolf@redhat.com>

On Mon, Jan 14, 2013 at 05:31:31PM +0100, Kevin Wolf wrote:
> One of the recent refactoring patches (commit f50f88b9) didn't take care
> to initialise l2meta properly, so with zero-length writes, which don't
> even enter the write loop, qemu just segfaulted.
> 
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
>  block/qcow2.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)

Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block

Stefan

      reply	other threads:[~2013-01-15  8:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14 16:31 [Qemu-devel] [PATCH] qcow2: Fix segfault on zero-length write Kevin Wolf
2013-01-15  8:17 ` Stefan Hajnoczi [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=20130115081701.GA21625@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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;
as well as URLs for NNTP newsgroup(s).