linux-kernel - Re: [BUG] Linux 2.6.28.4 freezing on a 32-bits x86 Thinkpad T43p

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090211201444.GA14274@amt.cnet>
Date:	Wed, 11 Feb 2009 18:14:44 -0200
From:	Marcelo Tosatti <mtosatti@...hat.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	Avi Kivity <avi@...hat.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>, Greg KH <greg@...ah.com>,
	ltt-dev@...ts.casi.polymtl.ca, linux-kernel@...r.kernel.org,
	kvm@...r.kernel.org
Subject: Re: [BUG] Linux 2.6.28.4 freezing on a 32-bits x86 Thinkpad T43p

On Wed, Feb 11, 2009 at 08:50:38PM +0100, Ingo Molnar wrote:
> 
> * Mathieu Desnoyers <mathieu.desnoyers@...ymtl.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.

This code is supposed to function on KVM guests only (kvm_mmu_pte_write
= paravirtual pte update).

There's some really screwed if its executing in a native machine.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/