Re: [PATCH backport hints for <3.10] KVM: x86: Convert vapic synchronization to _cached functions (CVE-2013-6368)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Il 16/12/2013 16:24, Greg KH ha scritto:
> On Mon, Dec 16, 2013 at 12:38:17PM +0100, Paolo Bonzini wrote:
>> The KVM patch "fix vapic memory corruption" applies to most kernels that
>> have KVM, but the fix does not apply on many older branches.  The APIs it
>> uses are available in 3.1, but until 3.9 kvm_gfn_to_hva_cache_init had
>> one fewer parameter.
>>
>> The comments in this patch should help fixing kvm_lapic_set_vapic_addr
>> in older kernels.  I will review the backports as they are posted to
>> LKML (if I am CCed...).
>>
>> Signed-off-by: Paolo Bonzini <pbonzini@xxxxxxxxxx>
>> ---
>>  arch/x86/kvm/lapic.c | 38 +++++++++++++++++++++++++++++---------
>>  arch/x86/kvm/lapic.h |  4 ++--
>>  arch/x86/kvm/x86.c   | 33 +--------------------------------
>>  3 files changed, 32 insertions(+), 43 deletions(-)
> 
> I don't understand, what are people supposed to do with this?

If people want to backport the patch to their stable tree, and the
upstream patch doesn't apply, they can use this as a skeleton.  I was
asked by Francis how to backport the patch, and I think code is a better
tool than text.

It's not a particularly important bug.  It's okay if you don't apply it
anywhere where it doesn't apply cleanly (i.e. 3.10 and newer only), but
the Debian and RT folks may disagree.  If they want to do the backport,
I hope this can help.

Paolo
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux