diff options
author | Markus Armbruster <armbru@redhat.com> | 2014-10-07 13:59:22 +0200 |
---|---|---|
committer | Kevin Wolf <kwolf@redhat.com> | 2014-10-20 14:03:50 +0200 |
commit | 26f8b3a84750546342d4397f86efb1ea7798d5dd (patch) | |
tree | 8fd070e6bda1831dcb46333569049e0f04c5d4d7 /qapi-schema.json | |
parent | d3aeb1b7dadacabd175efd515c7c52642141be87 (diff) | |
download | hqemu-26f8b3a84750546342d4397f86efb1ea7798d5dd.zip hqemu-26f8b3a84750546342d4397f86efb1ea7798d5dd.tar.gz |
blockdev: Fix blockdev-add not to create DriveInfo
blockdev_init() always creates a DriveInfo, but only drive_new() fills
it in. qmp_blockdev_add() leaves it blank. This results in a drive
with type = IF_IDE, bus = 0, unit = 0. Screwed up in commit ee13ed1c.
Board initialization code looking for IDE drive (0,0) can pick up one
of these bogus drives. The QMP command has to execute really early to
be visible. Not sure how likely that is in practice.
Fix by creating DriveInfo in drive_new(). Block backends created by
blockdev-add don't get one.
Breaks the test for "has been created by qmp_blockdev_add()" in
blockdev_mark_auto_del() and do_drive_del(), because it changes the
value of dinfo && !dinfo->enable_auto_del from true to false. Simply
test !dinfo instead.
Leaves DriveInfo member enable_auto_del unused. Drop it.
A few places assume a block backend always has a DriveInfo. Fix them
up.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'qapi-schema.json')
0 files changed, 0 insertions, 0 deletions