From: Kevin Wolf <kwolf@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, stefanha@gmail.com
Subject: [Qemu-devel] [PATCH v2 0/2] block: Fix multiwrite error handling
Date: Fri, 2 Jul 2010 14:07:35 +0200 [thread overview]
Message-ID: <1278072457-8156-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.
v2:
- Completely replaced patch 1 which Stefan found to be incorrect (thanks for
the good review!). Hope I've got it right this time.
Kevin Wolf (2):
block: Fix early failure in multiwrite
block: Handle multiwrite errors only when all requests have completed
block.c | 40 ++++++++++++++++++++++++++++++----------
1 files changed, 30 insertions(+), 10 deletions(-)
next reply other threads:[~2010-07-02 12:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 12:07 Kevin Wolf [this message]
2010-07-02 12:07 ` [Qemu-devel] [PATCH v2 1/2] block: Fix early failure in multiwrite Kevin Wolf
2010-07-02 13:18 ` [Qemu-devel] " Stefan Hajnoczi
2010-07-02 13:32 ` Kevin Wolf
2010-07-02 12:07 ` [Qemu-devel] [PATCH v2 2/2] block: Handle multiwrite errors only when all requests have completed Kevin Wolf
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=1278072457-8156-1-git-send-email-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).