linux-kernel - Re: [PATCH] KVM: selftests: Ensure all vCPUs hit -EFAULT during initial RO stage

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <174101637372.3904037.6271235554709270288.b4-ty@google.com>
Date: Tue,  4 Mar 2025 17:05:08 -0800
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, 
	Yan Zhao <yan.y.zhao@...el.com>
Subject: Re: [PATCH] KVM: selftests: Ensure all vCPUs hit -EFAULT during
 initial RO stage

On Fri, 28 Feb 2025 15:08:04 -0800, Sean Christopherson wrote:
> During the initial mprotect(RO) stage of mmu_stress_test, keep vCPUs
> spinning until all vCPUs have hit -EFAULT, i.e. until all vCPUs have tried
> to write to a read-only page.  If a vCPU manages to complete an entire
> iteration of the loop without hitting a read-only page, *and* the vCPU
> observes mprotect_ro_done before starting a second iteration, then the
> vCPU will prematurely fall through to GUEST_SYNC(3) (on x86 and arm64) and
> get out of sequence.
> 
> [...]

Applied to kvm-x86 fixes, with Fixes and Closes.  Thanks!

[1/1] KVM: selftests: Ensure all vCPUs hit -EFAULT during initial RO stage
      https://github.com/kvm-x86/linux/commit/d88ed5fb7c88

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