Linus Torvalds wrote:
quoted text >> We dont do any instruction decoding in #GP handlers to figure out what
>> happened, while in the pagefault case we know which address faulted,
>> etc.
>>
>
> Why would we care? It would be very obvious from the instruction
> disassembly plus the register contents. No need to decode instructions.
>
We could add a printk to the #GP handler that alerts the reader that a
poisoned list is suspected, if we find the address pattern in one of the
registers.
--
error compiling committee.c: too many arguments to function
--
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/
Messages in current thread:
Re: [git pull] core, x86: make LIST_POISON less deadly , Avi Kivity , (Mon Jul 14, 9:08 am)