From: Stefan Hajnoczi <stefanha@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
karl.heubaum@oracle.com, ameya.more@oracle.com,
Mark Kanda <mark.kanda@oracle.com>
Subject: Re: [Qemu-devel] [PATCH] virtio-blk: check for NULL BlockDriverState
Date: Wed, 24 Jan 2018 11:31:23 +0000 [thread overview]
Message-ID: <20180124113123.GB17193@stefanha-x1.localdomain> (raw)
In-Reply-To: <1516633309-20803-1-git-send-email-mark.kanda@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 1893 bytes --]
On Mon, Jan 22, 2018 at 09:01:49AM -0600, Mark Kanda wrote:
> Add a BlockDriverState NULL check to virtio_blk_handle_request()
> to prevent a segfault if the drive is forcibly removed using HMP
> 'drive_del' (without performing a hotplug 'device_del' first).
>
> Signed-off-by: Mark Kanda <mark.kanda@oracle.com>
> Reviewed-by: Karl Heubaum <karl.heubaum@oracle.com>
> Reviewed-by: Ameya More <ameya.more@oracle.com>
> ---
> hw/block/virtio-blk.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/hw/block/virtio-blk.c b/hw/block/virtio-blk.c
> index b1532e4..76ddbbf 100644
> --- a/hw/block/virtio-blk.c
> +++ b/hw/block/virtio-blk.c
> @@ -507,6 +507,13 @@ static int virtio_blk_handle_request(VirtIOBlockReq *req, MultiReqBuffer *mrb)
> return -1;
> }
>
> + /* If the drive was forcibly removed (e.g. HMP 'drive_del'), the block
> + * driver state may be NULL and there is nothing left to do. */
> + if (!blk_bs(req->dev->blk)) {
Adding Markus Armbruster to check my understanding of drive_del:
1. If id is a node name (e.g. created via blockdev-add) then attempting
to remove the root node produces the "Node %s is in use" error. In
that case this patch isn't needed.
2. If id is a BlockBackend (e.g. created via -drive) then removing the
root node is allowed. The BlockBackend stays in place but blk->root
becomes NULL, hence this patch is needed.
Markus: What are the valid use cases for #2? If blk->bs becomes NULL I
would think a lot more code beyond virtio-blk can segfault.
> + virtio_error(vdev, "virtio-blk BlockDriverState is NULL");
> + return -1;
> + }
> +
> /* We always touch the last byte, so just see how big in_iov is. */
> req->in_len = iov_size(in_iov, in_num);
> req->in = (void *)in_iov[in_num - 1].iov_base
> --
> 1.8.3.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2018-01-24 11:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 15:01 [Qemu-devel] [PATCH] virtio-blk: check for NULL BlockDriverState Mark Kanda
2018-01-24 11:31 ` Stefan Hajnoczi [this message]
2018-01-29 15:41 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2018-01-29 16:13 ` Mark Kanda
2018-02-01 17:58 ` Stefan Hajnoczi
2018-01-30 12:38 ` Stefan Hajnoczi
2018-01-30 15:56 ` Kevin Wolf
2018-01-30 19:04 ` John Snow
2018-02-01 18:00 ` Stefan Hajnoczi
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=20180124113123.GB17193@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=ameya.more@oracle.com \
--cc=armbru@redhat.com \
--cc=karl.heubaum@oracle.com \
--cc=mark.kanda@oracle.com \
--cc=qemu-block@nongnu.org \
--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).