qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: peter.maydell@linaro.org, qemu-devel@nongnu.org
Cc: Jason Wang <jasowang@redhat.com>,
	Shmulik Ladkani <shmulik.ladkani@ravellosystems.com>,
	Dana Rubin <dana.rubin@ravellosystems.com>
Subject: [Qemu-devel] [PULL 07/10] vmxnet3: Do not fill stats if device is inactive
Date: Tue, 27 Oct 2015 14:08:41 +0800	[thread overview]
Message-ID: <1445926124-30681-8-git-send-email-jasowang@redhat.com> (raw)
In-Reply-To: <1445926124-30681-1-git-send-email-jasowang@redhat.com>

From: Shmulik Ladkani <shmulik.ladkani@ravellosystems.com>

Guest OS may issue VMXNET3_CMD_GET_STATS even before device was
activated (for example in linux, after insmod but prior net-dev open).

Accessing shared descriptors prior device activation is illegal as the
VMXNET3State structures have not been fully initialized.

As a result, guest memory gets corrupted and may lead to guest OS
crashes.

Fix, by not filling the stats descriptors if device is inactive.

Reported-by: Leonid Shatz <leonid.shatz@ravellosystems.com>
Acked-by: Dmitry Fleytman <dmitry@daynix.com>
Signed-off-by: Dana Rubin <dana.rubin@ravellosystems.com>
Signed-off-by: Shmulik Ladkani <shmulik.ladkani@ravellosystems.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
---
 hw/net/vmxnet3.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/hw/net/vmxnet3.c b/hw/net/vmxnet3.c
index 3c5e10d..5e3a233 100644
--- a/hw/net/vmxnet3.c
+++ b/hw/net/vmxnet3.c
@@ -1289,6 +1289,10 @@ static uint32_t vmxnet3_get_interrupt_config(VMXNET3State *s)
 static void vmxnet3_fill_stats(VMXNET3State *s)
 {
     int i;
+
+    if (!s->device_active)
+        return;
+
     for (i = 0; i < s->txq_num; i++) {
         cpu_physical_memory_write(s->txq_descr[i].tx_stats_pa,
                                   &s->txq_descr[i].txq_stats,
-- 
2.1.4

  parent reply	other threads:[~2015-10-27  6:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-27  6:08 [Qemu-devel] [PULL 00/10] Net patches Jason Wang
2015-10-27  6:08 ` [Qemu-devel] [PULL 01/10] net: cadence_gem: Set initial MAC address Jason Wang
2015-10-27  6:08 ` [Qemu-devel] [PULL 02/10] net/dump: Add support for receive_iov function Jason Wang
2015-10-27  6:08 ` [Qemu-devel] [PULL 03/10] net/dump: Rework net-dump init functions Jason Wang
2015-10-27  6:08 ` [Qemu-devel] [PULL 04/10] net/dump: Separate the NetClientState from the DumpState Jason Wang
2015-10-27  6:08 ` [Qemu-devel] [PULL 05/10] net/dump: Provide the dumping facility as a net-filter Jason Wang
2015-10-27  6:08 ` [Qemu-devel] [PULL 06/10] options: Add documentation for filter-dump Jason Wang
2015-10-27  6:08 ` Jason Wang [this message]
2015-10-27  6:08 ` [Qemu-devel] [PULL 08/10] net: Remove duplicate data from query-rx-filter on multiqueue net devices Jason Wang
2015-10-27  6:08 ` [Qemu-devel] [PULL 09/10] net: make iov_to_buf take right size argument in nc_sendv_compat() Jason Wang
2015-10-27  6:08 ` [Qemu-devel] [PULL 10/10] net: free the string returned by object_get_canonical_path_component Jason Wang
2015-10-27 11:12 ` [Qemu-devel] [PULL 00/10] Net patches Peter Maydell

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=1445926124-30681-8-git-send-email-jasowang@redhat.com \
    --to=jasowang@redhat.com \
    --cc=dana.rubin@ravellosystems.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=shmulik.ladkani@ravellosystems.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).