diff options
| author | Marc Zyngier <maz@kernel.org> | 2026-10-15 11:05:36 +0100 |
|---|---|---|
| committer | Marc Zyngier <maz@kernel.org> | 2026-10-15 14:52:24 +0100 |
| commit | e64309198eda29415a95113def92aa40196cd422 (patch) | |
| tree | d6e0f114bb26e6b3385dc30104bc167c17644863 /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | 22b6557ad05bf05c73246f62c19af3e04017270e (diff) | |
KVM: arm64: Turn vcpu->arch.pause into a counter
We have situations where we can call kvm_arm_halt_guest() without
holding config_lock, which means that halt and resume can overlap in
funny ways when called from separate contexts, and result in situations
where a vcpu is resumed while other parts of KVM assume it is halted.
Consequences are left to the imagination of the reader.
Fix this sorry situation by turning kvm_vcpu_arch::pause into an
atomic counter, which makes the races described above harmless.
Fixes: 3b92830ad41b2 ("KVM: arm/arm64: implement kvm_arm_[halt,resume]_guest")
Reviewed-by: Fuad Tabba <fuad.tabba@linux.dev>
Tested-by: Fuad Tabba <fuad.tabba@linux.dev>
Cc: stable@vger.kernel.org
Link: https://patch.msgid.link/20261015100539.1011760-5-maz@kernel.org
Signed-off-by: Marc Zyngier <maz@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions
