From: Kevin Wolf <kwolf@redhat.com>
To: Ryan Harper <ryanh@us.ibm.com>
Cc: Stefan Hajnoczi <stefan.hajnoczi@uk.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] Don't allow multiwrites against a block device without underlying medium
Date: Tue, 08 Mar 2011 16:06:33 +0100 [thread overview]
Message-ID: <4D7645F9.7000909@redhat.com> (raw)
In-Reply-To: <20110307160104.GW23238@us.ibm.com>
Am 07.03.2011 17:01, schrieb Ryan Harper:
> If the block device has been closed, we no longer have a medium to submit
> IO against, check for this before submitting io. This prevents a segfault
> further in the code where we dereference elements of the block driver.
>
> Signed-off-by: Ryan Harper <ryanh@us.ibm.com>
Thanks, applied to the block branch.
Kevin
next prev parent reply other threads:[~2011-03-08 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 16:01 [Qemu-devel] [PATCH v2] Don't allow multiwrites against a block device without underlying medium Ryan Harper
2011-03-07 16:26 ` Stefan Hajnoczi
2011-03-07 16:27 ` Stefan Hajnoczi
2011-03-08 15:06 ` Kevin Wolf [this message]
2011-03-30 7:34 ` Markus Armbruster
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=4D7645F9.7000909@redhat.com \
--to=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ryanh@us.ibm.com \
--cc=stefan.hajnoczi@uk.ibm.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).