linux-kernel - [GIT PULL] KVM fixes for 2.6.30-rc7

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

Message-ID: <4A1AD274.6030305@redhat.com>
Date:	Mon, 25 May 2009 20:16:36 +0300
From:	Avi Kivity <avi@...hat.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	linux-kernel <linux-kernel@...r.kernel.org>,
	KVM list <kvm@...r.kernel.org>
Subject: [GIT PULL] KVM fixes for 2.6.30-rc7

Linus,

The upcoming F11 release has uncovered a couple of bugs relating to the 
reloading to the PDPTRs in PAE guests.  While the bugs are not recent 
regressions, the switch to PAE as a default kernel, coupled with the use 
of the fancy priority inherited futexes in audio code, cause the bug to 
start affecting people.

Futexes enter into the picture here as their initialization code 
deliberately writes into the NULL pointer.  If the PDPTRs have not been 
correctly reloaded, this write hits the low kernel mappings, and the 
write succeeds where the code expects it to fail, disabling the pi futex 
subsystem.

So please pull from

  git://git.kernel.org/pub/scm/virt/kvm/kvm.git kvm-updates/2.6.30

To get

Avi Kivity (2):
      KVM: Make paravirt tlb flush also reload the PAE PDPTRs
      KVM: Fix PDPTR reloading on CR4 writes

 arch/x86/kvm/mmu.c |    3 +--
 arch/x86/kvm/x86.c |    6 +++++-
 2 files changed, 6 insertions(+), 3 deletions(-)

-- 
error compiling committee.c: too many arguments to function

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