Since a double fault always implies that kernel data structures are corrupt, this fault should neither be handed to user mode handling, nor should the handler allow resuming the faulting code stream (since architecturally this isn't a fault, but an abort). Note that this slightly depends on the previously submitted patch adjusting the prototype of notify_die() (a compiler warning will result without that other patch). From: Jan Beulich <[email protected]> (actual patch attached)
Attachment:
linux-2.6.14-x86_64-doublefault.patch
Description: Binary data
- References:
- [PATCH] x86-64: separate unwind info generation from CONFIG_DEBUG_INFO
- From: "Jan Beulich" <[email protected]>
- [PATCH] x86-64: separate unwind info generation from CONFIG_DEBUG_INFO
- Prev by Date: [PATCH] x86-64: make trap information available to die notification handlers
- Next by Date: [PATCH] x86-64: remove unprotected iret
- Previous by thread: [PATCH] x86-64: make trap information available to die notification handlers
- Next by thread: [PATCH] x86-64: remove unprotected iret
- Index(es):
 |