WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] [PATCH] [XEN][ACM] fix missing spin_unlock

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH] [XEN][ACM] fix missing spin_unlock
From: Stefan Berger <stefanb@xxxxxxxxxx>
Date: Mon, 26 Feb 2007 14:57:08 -0500
Cc: sailer@xxxxxxxxxx
Delivery-date: Mon, 26 Feb 2007 11:53:18 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Insert a missing spin_unlock statement.

Signed-off-by: Stefan Berger <stefanb@xxxxxxxxxx>

Keir,

  I have a question regarding the event channel data structure. It looks
like a stale entry is in the event channel array indicating that a event
channel at a given port has a certain remote domain as target. However,
that domain does not exist anymore and therefore the code section where
I add the spin_unlock() call gets triggered now. Could this be a bug in
the domain-cleanup code?

  I can trigger this problem when running the xm-test suite with ACM
compiled into Xen. After 159 domains have been created, which happens to
be during the list tests, the stale port entry shows up and remains. The
list tests when run after a reboot do not trigger this, though.

  Stefan

Attachment: acm_missing_spin_unlock.diff
Description: Text Data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>