linux-kernel - [GIT PULL] KVM updates for 3.3-rc2

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: <4F2E5BB0.7040702@redhat.com>
Date:	Sun, 05 Feb 2012 12:36:32 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	KVM list <kvm@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Marcelo Tosatti <mtosatti@...hat.com>
Subject: [GIT PULL] KVM updates for 3.3-rc2

Linus, please pull from:

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

Fixing a regression with the PMU MSRs when PMU virtualization is
disabled, a guest-internal DoS with the SYSCALL instruction, and a dirty
memory logging race that may cause live migration to fail.

Gleb Natapov (1):
      KVM: do not #GP on perf MSR writes when vPMU is disabled

Stephan Bärwolf (2):
      KVM: x86: extend "struct x86_emulate_ops" with "get_cpuid"
      KVM: x86: fix missing checks in syscall emulation

Takuya Yoshikawa (1):
      KVM: Fix __set_bit() race in mark_page_dirty() during dirty logging

 arch/x86/include/asm/kvm_emulate.h |   16 +++++++++++
 arch/x86/kvm/emulate.c             |   51
++++++++++++++++++++++++++++++++++++
 arch/x86/kvm/x86.c                 |   45 +++++++++++++++++++++++++++++++
 virt/kvm/kvm_main.c                |    2 +-
 4 files changed, 113 insertions(+), 1 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/