qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] block: Fix multiwrite error handling
Date: Thu,  1 Jul 2010 16:31:56 +0200	[thread overview]
Message-ID: <1277994718-14443-1-git-send-email-kwolf@redhat.com> (raw)

The bdrv_aio_multiwrite error handling has some bugs that lead to premature
cleanup, causing use-after-free and double free problems.

Kevin Wolf (2):
  block: Fix too early free in multiwrite
  block: Handle multiwrite errors only when all requests have completed

 block.c |   11 +++--------
 1 files changed, 3 insertions(+), 8 deletions(-)

             reply	other threads:[~2010-07-01 14:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-01 14:31 Kevin Wolf [this message]
2010-07-01 14:31 ` [Qemu-devel] [PATCH 1/2] block: Fix too early free in multiwrite Kevin Wolf
2010-07-02  8:10   ` Stefan Hajnoczi
2010-07-02  9:38   ` Christoph Hellwig
2010-07-01 14:31 ` [Qemu-devel] [PATCH 2/2] block: Handle multiwrite errors only when all requests have completed Kevin Wolf
2010-07-02  8:33   ` Stefan Hajnoczi
2010-07-02  9:40   ` Christoph Hellwig

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=1277994718-14443-1-git-send-email-kwolf@redhat.com \
    --to=kwolf@redhat.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).