linux-kernel - Re: [PATCH 0/9 v3] KVM: Nested SVM fixes and tracepoint conversion

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] [day] [month] [year] [list]

Date:	Mon, 12 Oct 2009 15:37:40 -0300
From:	Marcelo Tosatti <mtosatti@...hat.com>
To:	Joerg Roedel <joerg.roedel@....com>
Cc:	Avi Kivity <avi@...hat.com>, Alexander Graf <agraf@...e.de>,
	kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/9 v3] KVM: Nested SVM fixes and tracepoint conversion

On Fri, Oct 09, 2009 at 04:08:24PM +0200, Joerg Roedel wrote:
> Hi Avi, Marcelo,
> 
> this series of patches contains bugfixes for the Nested SVM code and the
> conversion of Nested SVM debugging to tracepoints. The fixes are:
> 
> 	1) A patch Alex already sent (1/9) but which was not yet
> 	   applied. It fixes a lost event_inj problem when we emulate a
> 	   vmrun and a vmexit without entering the guest in the
> 	   meantime.
> 
> 	2) The patch 2/9 fixes a schedule() while atomic bug in the
> 	   Nested SVM code. The KVM interrupt injection code runs with
> 	   preemtion and interrupts disabled. But the
> 	   enable_irq_window() function from SVM may emulate a #vmexit.
> 	   This emulation might sleep which causes the schedule() while
> 	   atomic() bug.
> 
> These fixes (patches 1 and 2) should also be considered for -stable
> backporting.  The patches 3 to 8 convert the old printk based debugging
> for Nested SVM to tracepoints.  Patch 9 removes the nsvm_printk code.
> Please review and/or consider to apply these changes.

Applied, thanks.

--
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/