* Mathieu Desnoyers <mathieu.desnoy...@polymtl.ca> wrote:
> Here is a new backtrace, taken with a huge amount of debugging active, which
> still
> points to an interrupt handler nested over kvm_mmu_pte_write as the culprit.
> It's
> weird that the kvm code gets called on my modest Pentium M laptop, which I
> think
> has no VT-x support at all. I am not running any KVM VMs on this machine. The
> problem still happens on 2.6.28.4, and Slub redzones did not identify any
> memory
> corruption. This could be due to kvm_mmu_pte_write which either should not be
> called at all, or due to improper interrupt disabling in this function.
Does latest tip:master fix it? In particular this one:
9cf161a: x86/cpa: make sure cpa is safe to call in lazy mmu mode
fixes a crasher related to KVM and mmu notifiers ...
Ingo
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
