From: Dor Laor <dor.laor@gmail.com>
To: kvm-devel <kvm-devel@lists.sourceforge.net>,
Anthony Liguori <aliguori@us.ibm.com>
Subject: [PATCH] Check device status in tx timer
Date: Tue, 04 Mar 2008 17:33:26 +0200 [thread overview]
Message-ID: <1204644806.19089.44.camel@localhost.localdomain> (raw)
repository: /home/dor/src/merge/kvm
branch: trunk
commit acdb6d2aa7332179eead306ead17494ae23edbd6
Author: Dor Laor <dor.laor@qumranet.com>
Date: Tue Mar 4 08:16:06 2008 -0500
Check device status in tx timer.
The device can be down when the timer pops.
If it is down it will cause segfault.
It might happen on migration but also on regular operation
when the device sends packets and quickly goes down before
the host timer pops.
Signed-off-by: Dor Laor <dor.laor@qumranet.com>
diff --git a/qemu/hw/virtio-net.c b/qemu/hw/virtio-net.c
index 612cf6b..a05eafb 100644
--- a/qemu/hw/virtio-net.c
+++ b/qemu/hw/virtio-net.c
@@ -280,6 +280,10 @@ static void virtio_net_tx_timer(void *opaque)
{
VirtIONet *n = opaque;
+ /* Just in case the driver is not ready on more */
+ if (!(n->vdev.status & VIRTIO_CONFIG_S_DRIVER_OK))
+ return;
+
n->tx_vq->vring.used->flags &= ~VRING_USED_F_NO_NOTIFY;
n->tx_timer_active = 0;
virtio_net_flush_tx(n, n->tx_vq);
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next reply other threads:[~2008-03-04 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 15:33 Dor Laor [this message]
[not found] ` <47CD6DCF.7030008@us.ibm.com>
2008-03-04 22:39 ` [PATCH] Check device status in tx timer Dor Laor
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=1204644806.19089.44.camel@localhost.localdomain \
--to=dor.laor@gmail.com \
--cc=aliguori@us.ibm.com \
--cc=dor.laor@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
/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