From: mdroth <mdroth@linux.vnet.ibm.com>
To: pbonzini@redhat.com
Cc: Markus Armbruster <armbru@redhat.com>,
qemu-stable@nongnu.org, Nicholas Bellinger <nab@linux-iscsi.org>,
qemu-devel@nongnu.org, stefanha@redhat.com,
Asias He <asias@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/3] vhost-scsi: fix k->set_guest_notifiers() NULL dereference
Date: Tue, 11 Jun 2013 17:58:05 -0500 [thread overview]
Message-ID: <20130611225805.GD12585@vm> (raw)
In-Reply-To: <1369923286-22260-2-git-send-email-stefanha@redhat.com>
On Thu, May 30, 2013 at 04:14:44PM +0200, Stefan Hajnoczi wrote:
> Coverity picked up a copy-paste bug. In vhost_scsi_start() we check for
> !k->set_guest_notifiers and error out. The check probably got copied
> but instead of erroring we actually use the function pointer!
>
> Cc: Nicholas Bellinger <nab@linux-iscsi.org>
> Cc: Asias He <asias@redhat.com>
> Cc: qemu-stable@nongnu.org
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Hi Paolo,
Looking to pick this up for 1.5.1 along with a few other goodies in your
scsi branch:
iscsi: reorganize iscsi_readcapacity_sync
iscsi: simplify freeing of tasks
scsi-disk: scsi-block device for scsi pass-through should not be remo…
scsi-generic: check the return value of bdrv_aio_ioctl in execute_com…
scsi-generic: fix sign extension of READ CAPACITY(10) data
scsi: reset cdrom tray statuses on scsi_disk_reset
Freeze for 1.5.1 is planned for June 19. Willing to pluck from
maintainer branches for the more important ones but would prefer
upstream if you can send a PULL for these.
> ---
> hw/scsi/vhost-scsi.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/scsi/vhost-scsi.c b/hw/scsi/vhost-scsi.c
> index d7a1c33..785e93f 100644
> --- a/hw/scsi/vhost-scsi.c
> +++ b/hw/scsi/vhost-scsi.c
> @@ -123,7 +123,7 @@ static void vhost_scsi_stop(VHostSCSI *s)
> VirtioBusClass *k = VIRTIO_BUS_GET_CLASS(qbus);
> int ret = 0;
>
> - if (!k->set_guest_notifiers) {
> + if (k->set_guest_notifiers) {
> ret = k->set_guest_notifiers(qbus->parent, s->dev.nvqs, false);
> if (ret < 0) {
> error_report("vhost guest notifier cleanup failed: %d\n", ret);
> --
> 1.8.1.4
>
>
next prev parent reply other threads:[~2013-06-11 22:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 14:14 [Qemu-devel] [PATCH 0/3] vhost-scsi, ivshmem, savevm fixes for Coverity issues Stefan Hajnoczi
2013-05-30 14:14 ` [Qemu-devel] [PATCH 1/3] vhost-scsi: fix k->set_guest_notifiers() NULL dereference Stefan Hajnoczi
2013-06-11 22:58 ` mdroth [this message]
2013-06-12 12:47 ` Paolo Bonzini
2013-05-30 14:14 ` [Qemu-devel] [PATCH 2/3] ivshmem: add missing error exit(2) Stefan Hajnoczi
2013-06-03 12:22 ` Markus Armbruster
2013-05-30 14:14 ` [Qemu-devel] [PATCH 3/3] savevm: avoid leaking popen(3) file pointer Stefan Hajnoczi
2013-05-30 14:25 ` Eric Blake
2013-05-30 19:34 ` Stefan Hajnoczi
2013-06-11 22:59 ` [Qemu-devel] [Qemu-stable] " mdroth
2013-06-12 7:16 ` 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=20130611225805.GD12585@vm \
--to=mdroth@linux.vnet.ibm.com \
--cc=armbru@redhat.com \
--cc=asias@redhat.com \
--cc=nab@linux-iscsi.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=stefanha@redhat.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).