qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, jsnow@redhat.com
Subject: [Qemu-devel] [PULL 4/9] block-backend: Always notify on blk_eject
Date: Fri, 11 Nov 2016 13:49:50 -0500	[thread overview]
Message-ID: <1478890195-30841-5-git-send-email-jsnow@redhat.com> (raw)
In-Reply-To: <1478890195-30841-1-git-send-email-jsnow@redhat.com>

blk_eject is only used by scsi-disk and atapi, and in both cases we
only attempt to invoke blk_eject if we have a bona-fide change in
tray state.

The "issue" here is that the tray state does not generate a QMP event
unless there is a medium/BDS attached to the device, so if libvirt et al
are waiting for a tray event to occur from an empty-but-closed drive,
software opening that drive will not emit an event and libvirt will
wait forever.

Change this by modifying blk_eject to always emit an event, instead of
conditionally on a "real" backend eject.

Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1373264

Reported-by: Peter Krempa <pkrempa@redhat.com>
Signed-off-by: John Snow <jsnow@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Message-id: 1478553214-497-2-git-send-email-jsnow@redhat.com
Signed-off-by: John Snow <jsnow@redhat.com>
---
 block/block-backend.c | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/block/block-backend.c b/block/block-backend.c
index 27a7f6f..efbf398 100644
--- a/block/block-backend.c
+++ b/block/block-backend.c
@@ -1393,13 +1393,14 @@ void blk_eject(BlockBackend *blk, bool eject_flag)
 
     if (bs) {
         bdrv_eject(bs, eject_flag);
-
-        id = blk_get_attached_dev_id(blk);
-        qapi_event_send_device_tray_moved(blk_name(blk), id,
-                                          eject_flag, &error_abort);
-        g_free(id);
-
     }
+
+    /* Whether or not we ejected on the backend,
+     * the frontend experienced a tray event. */
+    id = blk_get_attached_dev_id(blk);
+    qapi_event_send_device_tray_moved(blk_name(blk), id,
+                                      eject_flag, &error_abort);
+    g_free(id);
 }
 
 int blk_get_flags(BlockBackend *blk)
-- 
2.7.4

  parent reply	other threads:[~2016-11-11 18:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-11 18:49 [Qemu-devel] [PULL 0/9] Ide patches John Snow
2016-11-11 18:49 ` [Qemu-devel] [PULL 1/9] atapi: classify read_cd as conditionally returning data John Snow
2016-11-11 18:49 ` [Qemu-devel] [PULL 2/9] ahci-test: Create smaller test ISO images John Snow
2016-11-11 18:49 ` [Qemu-devel] [PULL 3/9] ahci-test: test atapi read_cd with bcl, nb_sectors = 0 John Snow
2016-11-11 18:49 ` John Snow [this message]
2016-11-11 18:49 ` [Qemu-devel] [PULL 5/9] libqtest: add qmp_eventwait_ref John Snow
2016-11-11 18:49 ` [Qemu-devel] [PULL 6/9] libqos/ahci: Support expected errors John Snow
2016-11-11 18:49 ` [Qemu-devel] [PULL 7/9] libqos/ahci: Add ATAPI tray macros John Snow
2016-11-11 18:49 ` [Qemu-devel] [PULL 8/9] libqos/ahci: Add get_sense and test_ready John Snow
2016-11-11 18:49 ` [Qemu-devel] [PULL 9/9] ahci-test: add QMP tray test for ATAPI John Snow
2016-11-13  3:32 ` [Qemu-devel] [PULL 0/9] Ide patches no-reply

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=1478890195-30841-5-git-send-email-jsnow@redhat.com \
    --to=jsnow@redhat.com \
    --cc=peter.maydell@linaro.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).