Continuing on the stack saved by __prepare_to_wait() on the wrong cpu is rather dangerous.
Instead of doing so just call the scheduler again as it already is happening in the similar case in __prepare_to_wait() when doing the setjmp() would be wrong. Signed-off-by: Juergen Gross <[email protected]> --- xen/common/wait.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/xen/common/wait.c b/xen/common/wait.c index 3fc5f68611..24716e7676 100644 --- a/xen/common/wait.c +++ b/xen/common/wait.c @@ -196,6 +196,11 @@ void check_wakeup_from_wait(void) { gdprintk(XENLOG_ERR, "vcpu affinity lost\n"); domain_crash(curr->domain); + + /* Re-initiate scheduler and don't longjmp(). */ + raise_softirq(SCHEDULE_SOFTIRQ); + for ( ; ; ) + do_softirq(); } /* -- 2.16.4 _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
