diff options
| author | David Matlack <dmatlack@google.com> | 2024-05-03 20:17:32 +0200 |
|---|---|---|
| committer | Sean Christopherson <seanjc@google.com> | 2024-06-18 18:20:01 +0200 |
| commit | a6816314af5749cd88944bfdceb270c627cdf348 (patch) | |
| tree | e082018db936c3d3be6219608524d8a508b1c259 /mm/show_mem.c | |
| parent | KVM: selftests: Test vCPU boot IDs above 2^32 and MAX_VCPU_ID (diff) | |
| download | linux-a6816314af5749cd88944bfdceb270c627cdf348.tar.xz linux-a6816314af5749cd88944bfdceb270c627cdf348.zip | |
KVM: Introduce vcpu->wants_to_run
Introduce vcpu->wants_to_run to indicate when a vCPU is in its core run
loop, i.e. when the vCPU is running the KVM_RUN ioctl and immediate_exit
was not set.
Replace all references to vcpu->run->immediate_exit with
!vcpu->wants_to_run to avoid TOCTOU races with userspace. For example, a
malicious userspace could invoked KVM_RUN with immediate_exit=true and
then after KVM reads it to set wants_to_run=false, flip it to false.
This would result in the vCPU running in KVM_RUN with
wants_to_run=false. This wouldn't cause any real bugs today but is a
dangerous landmine.
Signed-off-by: David Matlack <dmatlack@google.com>
Link: https://lore.kernel.org/r/20240503181734.1467938-2-dmatlack@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'mm/show_mem.c')
0 files changed, 0 insertions, 0 deletions