|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH] stack overflow during pv-guest restore
Jan (& Keir) That's what I did the first time (used a simple static) I generated a fix & tested it, because a lock is taken out (long) before __cpu_up() is invoked, to ensure only one cpu is in that code path anyhow. *But* as I explained below, a modified version of cpu_initialize_context() was already upstream and it went with a kzalloc-kfree implementation, so maybe you want to ask Jeremy why he didn't go with a simple static as well. So, the bottom line: the fix tries to follow upstream... typically that's what we do (or change upstream, so all of us can follow it). - Don Jan Beulich wrote: I think this can be fixed with a much smaller change: Since the only caller of cpu_initialize_context() is __cpu_up(), and since __cpu_up() invocation is serialized, the variable in question could simply be static. JanDon Dutile <ddutile@xxxxxxxxxx> 31.01.08 21:05 >>> _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |