summaryrefslogtreecommitdiffstats
path: root/include/linux/glob.h
diff options
context:
space:
mode:
authorRadim Krcmar2019-08-14 05:37:37 +0200
committerPaolo Bonzini2019-08-14 16:28:33 +0200
commitb14c876b994f208b6b95c222056e1deb0a45de0e (patch)
treeb8216206a6dba93f225ce669c67a5c5301e3bba6 /include/linux/glob.h
parentMerge tag 'kvmarm-fixes-for-5.3-2' of git://git.kernel.org/pub/scm/linux/kern... (diff)
downloadkernel-qcow2-linux-b14c876b994f208b6b95c222056e1deb0a45de0e.tar.gz
kernel-qcow2-linux-b14c876b994f208b6b95c222056e1deb0a45de0e.tar.xz
kernel-qcow2-linux-b14c876b994f208b6b95c222056e1deb0a45de0e.zip
kvm: x86: skip populating logical dest map if apic is not sw enabled
recalculate_apic_map does not santize ldr and it's possible that multiple bits are set. In that case, a previous valid entry can potentially be overwritten by an invalid one. This condition is hit when booting a 32 bit, >8 CPU, RHEL6 guest and then triggering a crash to boot a kdump kernel. This is the sequence of events: 1. Linux boots in bigsmp mode and enables PhysFlat, however, it still writes to the LDR which probably will never be used. 2. However, when booting into kdump, the stale LDR values remain as they are not cleared by the guest and there isn't a apic reset. 3. kdump boots with 1 cpu, and uses Logical Destination Mode but the logical map has been overwritten and points to an inactive vcpu. Signed-off-by: Radim Krcmar <rkrcmar@redhat.com> Signed-off-by: Bandan Das <bsd@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'include/linux/glob.h')
0 files changed, 0 insertions, 0 deletions