* Chuck Ebbert <cebbert@redhat.com> wrote:

quoted text
> Ingo Molnar wrote:
>>
>> All CPUs hitting a double fault simultaneously and corrupting each  
>> others' kernel stack is a theoretical possibility - but is handling it  
>> worth the complexity? It appears to me that a lock plus a short stub  
>> function that takes the lock (with no stack usage) would handle that  
>> much better.
>
> That can't happen now because the TSS gets marked busy so we will get 
> a triple fault instead. One thing we might want to do in the current 
> code is unset the busy flag after handling the fault and before we 
> start looping at the end of the handler so we can handle another fault 
> later.

that would be a nice improvement.

	Ingo
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/