linux-kernel - [GIT PULL] KVM fixes for 2.6.28-rc

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]

Date:	Wed, 12 Nov 2008 11:34:15 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, kvm@...r.kernel.org
Subject: [GIT PULL] KVM fixes for 2.6.28-rc

Linus, please pull from the repo and branch at:

  git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git kvm-updates/2.6.28

to receive the current batch of KVM fixes.  These include a fix for a host
oops under heavy guest loads, memory attribute inconsistency fix with
Nehalem processors, a signal handling fix for ia64, and a few minor fixes.

Avi Kivity (2):
      KVM: Require the PCI subsystem
      KVM: Fix pit memory leak if unable to allocate irq source id

Marcelo Tosatti (1):
      KVM: MMU: increase per-vcpu rmap cache alloc size

Rakib Mullick (1):
      x86: KVM guest: fix section mismatch warning in kvmclock.c

Sheng Yang (1):
      KVM: VMX: Set IGMT bit in EPT entry

Xiantao Zhang (2):
      KVM: ia64: Use guest signal mask when blocking
      KVM: ia64: fix vmm_spin_{un}lock for !CONFIG_SMP

 arch/ia64/kvm/Kconfig      |    2 ++
 arch/ia64/kvm/kvm-ia64.c   |   12 ++++++------
 arch/ia64/kvm/vcpu.h       |    5 +++++
 arch/x86/kernel/kvmclock.c |    2 +-
 arch/x86/kvm/Kconfig       |    2 ++
 arch/x86/kvm/i8254.c       |    4 +++-
 arch/x86/kvm/mmu.c         |    2 +-
 arch/x86/kvm/vmx.c         |    3 ++-
 arch/x86/kvm/vmx.h         |    1 +
 9 files changed, 23 insertions(+), 10 deletions(-)
--
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/