[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <171262709411.1419562.9904481502027764758.b4-ty@google.com>
Date: Mon, 8 Apr 2024 19:01:31 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Sean Christopherson <seanjc@...gle.com>, Paolo Bonzini <pbonzini@...hat.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
syzbot+106a4f72b0474e1d1b33@...kaller.appspotmail.com,
David Woodhouse <dwmw2@...radead.org>, Paul Durrant <paul@....org>
Subject: Re: [PATCH 0/3] KVM: Fix for a mostly benign gpc WARN
On Tue, 19 Mar 2024 17:15:39 -0700, Sean Christopherson wrote:
> Fix a bug found by syzkaller, thanks to a new WARN sanity check, where KVM
> marks a gfn_to_pfn_cache as active without actually setting gpc->gpa or any
> other metadata. On top, harden against _directly_ setting gpc->gpa to KVM's
> magic INVALID_GPA, which would also fail the sanity check.
>
> Sean Christopherson (3):
> KVM: Add helpers to consolidate gfn_to_pfn_cache's page split check
> KVM: Check validity of offset+length of gfn_to_pfn_cache prior to
> activation
> KVM: Explicitly disallow activatating a gfn_to_pfn_cache with
> INVALID_GPA
>
> [...]
Applied to kvm-x86 fixes, thanks!
[1/3] KVM: Add helpers to consolidate gfn_to_pfn_cache's page split check
https://github.com/kvm-x86/linux/commit/18f06e976925
[2/3] KVM: Check validity of offset+length of gfn_to_pfn_cache prior to activation
https://github.com/kvm-x86/linux/commit/5c9ca4ed8908
[3/3] KVM: Explicitly disallow activatating a gfn_to_pfn_cache with INVALID_GPA
https://github.com/kvm-x86/linux/commit/fc62a4e8dee2
--
https://github.com/kvm-x86/linux/tree/next
Powered by blists - more mailing lists