From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, stefanha@gmail.com, hare@suse.de
Subject: [Qemu-devel] [PATCH v2 01/11] scsi hotplug: Set DriveInfo member bus correctly
Date: Fri, 28 Jan 2011 11:21:36 +0100 [thread overview]
Message-ID: <1296210106-11145-2-git-send-email-armbru@redhat.com> (raw)
In-Reply-To: <1296210106-11145-1-git-send-email-armbru@redhat.com>
drive_init() picks the first free bus and unit number, unless the user
specifies them.
This isn't a good fit for the drive_add monitor command, because there
we specify the controller by PCI address instead of using bus number
set by drive_init().
scsi_hot_add() takes care to replace the unit number set by
drive_init() by the real one, but it neglects to replace the bus
number. Thus, bus/unit in DriveInfo may be bogus. Affects
drive_get() and drive_get_max_bus(). I'm not aware of anything bad
happening because of that; looks like by the time we're hot-plugging,
the two functions aren't used anymore. Fix it anyway.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
---
hw/pci-hotplug.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/hw/pci-hotplug.c b/hw/pci-hotplug.c
index 270a982..b6dcbda 100644
--- a/hw/pci-hotplug.c
+++ b/hw/pci-hotplug.c
@@ -90,6 +90,7 @@ static int scsi_hot_add(Monitor *mon, DeviceState *adapter,
* specified).
*/
dinfo->unit = qemu_opt_get_number(dinfo->opts, "unit", -1);
+ dinfo->bus = scsibus->busnr;
scsidev = scsi_bus_legacy_add_drive(scsibus, dinfo->bdrv, dinfo->unit, false);
if (!scsidev) {
return -1;
--
1.7.2.3
next prev parent reply other threads:[~2011-01-28 10:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 10:21 [Qemu-devel] [PATCH v2 00/11] -drive/drive_add fixes and cleanups Markus Armbruster
2011-01-28 10:21 ` Markus Armbruster [this message]
2011-01-28 10:21 ` [Qemu-devel] [PATCH v2 02/11] blockdev: New drive_get_next(), replacing qdev_init_bdrv() Markus Armbruster
2011-01-28 10:21 ` [Qemu-devel] [PATCH v2 03/11] blockdev: Move BlockInterfaceType from qemu-common.h to blockdev.h Markus Armbruster
2011-01-28 10:21 ` [Qemu-devel] [PATCH v2 04/11] blockdev: Put BlockInterfaceType names and max_devs in tables Markus Armbruster
2011-01-28 10:21 ` [Qemu-devel] [PATCH v2 05/11] blockdev: Fix regression in -drive if=scsi, index=N Markus Armbruster
2011-01-28 10:21 ` [Qemu-devel] [PATCH v2 06/11] blockdev: Make drive_add() take explicit type, index parameters Markus Armbruster
2011-01-28 10:21 ` [Qemu-devel] [PATCH v2 07/11] blockdev: Replace drive_add()'s fmt, ... by optstr parameter Markus Armbruster
2011-01-31 10:50 ` [Qemu-devel] [PATCH v3 " Markus Armbruster
2011-01-28 10:21 ` [Qemu-devel] [PATCH v2 08/11] blockdev: Factor drive_index_to_{bus, unit}_id out of drive_init() Markus Armbruster
2011-01-28 10:21 ` [Qemu-devel] [PATCH v2 09/11] blockdev: New drive_get_by_index() Markus Armbruster
2011-01-28 10:21 ` [Qemu-devel] [PATCH v2 10/11] blockdev: Reject multiple definitions for the same drive Markus Armbruster
2011-01-28 10:21 ` [Qemu-devel] [PATCH v2 11/11] blockdev: Fix drive_add for drives without media Markus Armbruster
2011-01-31 11:00 ` [Qemu-devel] Re: [PATCH v2 00/11] -drive/drive_add fixes and cleanups 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=1296210106-11145-2-git-send-email-armbru@redhat.com \
--to=armbru@redhat.com \
--cc=hare@suse.de \
--cc=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).