On Tue, Oct 08, 2019 at 06:15:27PM -0400, Sasha Levin wrote: > On Tue, Oct 08, 2019 at 09:21:51AM +0200, gregkh@xxxxxxxxxxxxxxxxxxx wrote: > > > > The patch below does not apply to the 5.3-stable tree. > > If someone wants it applied there, or to any other stable or longterm > > tree, then please email the backport, including the original git commit > > id to <stable@xxxxxxxxxxxxxxx>. > > > > thanks, > > > > greg k-h > > > > ------------------ original commit in Linus's tree ------------------ > > > > > From 567926cca99ba1750be8aae9c4178796bf9bb90b Mon Sep 17 00:00:00 2001 > > From: Sean Christopherson <sean.j.christopherson@xxxxxxxxx> > > Date: Tue, 1 Oct 2019 09:21:23 -0700 > > Subject: [PATCH] KVM: nVMX: Fix consistency check on injected exception error > > code > > > > Current versions of Intel's SDM incorrectly state that "bits 31:15 of > > the VM-Entry exception error-code field" must be zero. In reality, bits > > 31:16 must be zero, i.e. error codes are 16-bit values. > > > > The bogus error code check manifests as an unexpected VM-Entry failure > > due to an invalid code field (error number 7) in L1, e.g. when injecting > > a #GP with error_code=0x9f00. > > > > Nadav previously reported the bug[*], both to KVM and Intel, and fixed > > the associated kvm-unit-test. > > > > [*] https://patchwork.kernel.org/patch/11124749/ > > > > Reported-by: Nadav Amit <namit@xxxxxxxxxx> > > Cc: stable@xxxxxxxxxxxxxxx > > Signed-off-by: Sean Christopherson <sean.j.christopherson@xxxxxxxxx> > > Reviewed-by: Jim Mattson <jmattson@xxxxxxxxxx> > > Signed-off-by: Paolo Bonzini <pbonzini@xxxxxxxxxx> > > There were minor conflicts due to missing tracepoint in 5.3 and code > movement in 4.19. I've fixed it up. Thanks for fixing these, and all of the other FAILED: issues. thanks, greg k-h
