Received-SPF: pass (google.com: domain of linux-kernel+bounces-168260-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Date: Fri,  3 May 2024 14:32:24 -0700
In-Reply-To: <20240423193114.2887673-1-seanjc@google.com>
Precedence: bulk
Mime-Version: 1.0
References: <20240423193114.2887673-1-seanjc@google.com>
Message-ID: <171469177238.1010157.17892485185197174264.b4-ty@google.com>
Subject: Re: [PATCH v3] KVM: x86/mmu: Fix a largely theoretical race in kvm_mmu_track_write()
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
Content-Type: text/plain; charset="utf-8"

On Tue, 23 Apr 2024 12:31:14 -0700, Sean Christopherson wrote:
> Add full memory barriers in kvm_mmu_track_write() and account_shadowed()
> to plug a (very, very theoretical) race where kvm_mmu_track_write() could
> miss a 0->1 transition of indirect_shadow_pages and fail to zap relevant,
> *stale* SPTEs.
> 
> Without the barriers, because modern x86 CPUs allow (per the SDM):
> 
> [...]

Applied to kvm-x86 mmu.

[1/1] KVM: x86/mmu: Fix a largely theoretical race in kvm_mmu_track_write()
      https://github.com/kvm-x86/linux/commit/226d9b8f1688

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