Received-SPF: pass (google.com: domain of linux-kernel+bounces-215613-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Date: Fri, 14 Jun 2024 17:02:55 -0700
In-Reply-To: <20240608001108.3296879-1-seanjc@google.com>
Precedence: bulk
Mime-Version: 1.0
References: <20240608001108.3296879-1-seanjc@google.com>
Message-ID: <171840976799.1411209.2253384085532260534.b4-ty@google.com>
Subject: Re: [PATCH] KVM: x86/mmu: Rephrase comment about synthetic PFERR
 flags in #PF handler
From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>, Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, 
	Xiaoyao Li <xiaoyao.li@intel.com>
Content-Type: text/plain; charset="utf-8"

On Fri, 07 Jun 2024 17:11:08 -0700, Sean Christopherson wrote:
> Reword the BUILD_BUG_ON() comment in the legacy #PF handler to explicitly
> describe how asserting that synthetic PFERR flags are limited to bits 31:0
> protects KVM against inadvertently passing a synthetic flag to the common
> page fault handler.
> 
> No functional change intended.
> 
> [...]

Applied to kvm-x86 mmu, thanks!

[1/1] KVM: x86/mmu: Rephrase comment about synthetic PFERR flags in #PF handler
      https://github.com/kvm-x86/linux/commit/caa727882937

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