From: "Eugene (jno) Dvurechenski" <jno@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-stable@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: [Qemu-devel] [PATCH 0/1] (for-2.5) Don't allow a guest to crash QEMU
Date: Thu, 26 Nov 2015 15:45:34 +0100 [thread overview]
Message-ID: <1448549135-6582-1-git-send-email-jno@linux.vnet.ibm.com> (raw)
I've found the case where erratic guest was able to crash QEMU.
This patch prevents dereferencing of a NULL pointer (empty 'd'
in the assertion, no valid LUN was specified).
Eugene (jno) Dvurechenski (1):
virtio-scsi: don't crash without a valid device
hw/scsi/virtio-scsi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.3.9
next reply other threads:[~2015-11-26 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 14:45 Eugene (jno) Dvurechenski [this message]
2015-11-26 14:45 ` [Qemu-devel] [PATCH v1 1/1] (for-2.5) virtio-scsi: don't crash without a valid device Eugene (jno) Dvurechenski
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=1448549135-6582-1-git-send-email-jno@linux.vnet.ibm.com \
--to=jno@linux.vnet.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).