|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] [PATCH] [XEN][ACM] fix missing spin_unlock
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
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>
|
- [Xen-devel] [PATCH] [XEN][ACM] fix missing spin_unlock,
Stefan Berger <=
|
|
|
|
|