Received-SPF: pass (google.com: domain of linux-kernel+bounces-136114-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Date: Mon,  8 Apr 2024 19:01:25 -0700
In-Reply-To: <20240314212902.2762507-1-rick.p.edgecombe@intel.com>
Precedence: bulk
Mime-Version: 1.0
References: <20240314212902.2762507-1-rick.p.edgecombe@intel.com>
Message-ID: <171262711269.1419750.7343660666296265143.b4-ty@google.com>
Subject: Re: [PATCH v2] KVM: x86/mmu: x86: Don't overflow lpage_info when
 checking attributes
From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>, pbonzini@redhat.com, chao.p.peng@linux.intel.com, 
	isaku.yamahata@intel.com, Rick Edgecombe <rick.p.edgecombe@intel.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="utf-8"

On Thu, 14 Mar 2024 14:29:02 -0700, Rick Edgecombe wrote:
> Fix KVM_SET_MEMORY_ATTRIBUTES to not overflow lpage_info array and trigger
> KASAN splat, as seen in the private_mem_conversions_test selftest.
> 
> When memory attributes are set on a GFN range, that range will have
> specific properties applied to the TDP. A huge page cannot be used when
> the attributes are inconsistent, so they are disabled for those the
> specific huge pages. For internal KVM reasons, huge pages are also not
> allowed to span adjacent memslots regardless of whether the backing memory
> could be mapped as huge.
> 
> [...]

Applied to kvm-x86 fixes, thanks!

[1/1] KVM: x86/mmu: x86: Don't overflow lpage_info when checking attributes
      https://github.com/kvm-x86/linux/commit/992b54bd083c

--
https://github.com/kvm-x86/linux/tree/next