[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-changelog] [xen-unstable] notify_via_xen_event_channel() should check for dying domain.



# HG changeset patch
# User Keir Fraser <keir.fraser@xxxxxxxxxx>
# Date 1284535133 -3600
# Node ID 62edd2611cbbe4c50574b6f6f73dda2ae1136dde
# Parent  869a0fdf8686c3dada14122df6d22a38705c2401
notify_via_xen_event_channel() should check for dying domain.

Else we can fail on either ASSERTion in that function.

From: Olaf Hering <olaf@xxxxxxxxx>
Signed-off-by: Keir Fraser <keir.fraser@xxxxxxxxxx>
---
 xen/common/event_channel.c |    6 ++++++
 1 files changed, 6 insertions(+)

diff -r 869a0fdf8686 -r 62edd2611cbb xen/common/event_channel.c
--- a/xen/common/event_channel.c        Wed Sep 15 07:48:27 2010 +0100
+++ b/xen/common/event_channel.c        Wed Sep 15 08:18:53 2010 +0100
@@ -1030,6 +1030,12 @@ void notify_via_xen_event_channel(struct
 
     spin_lock(&ld->event_lock);
 
+    if ( unlikely(ld->is_dying) )
+    {
+        spin_unlock(&ld->event_lock);
+        return;
+    }
+
     ASSERT(port_is_valid(ld, lport));
     lchn = evtchn_from_port(ld, lport);
     ASSERT(lchn->consumer_is_xen);

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.