diff options
| author | Sean Christopherson <[email protected]> | 2022-04-15 00:43:41 +0000 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2022-04-21 13:16:10 -0400 |
| commit | 2d08935682ac5f6bfb70f7e6844ec27d4a245fa4 (patch) | |
| tree | b4c9319b2267ebb8baf7986d0a87316c27f53440 /lib/test_fortify/write_overflow-strlcpy-src.c | |
| parent | 012c722569f171d58169606908ebbb8713f1609e (diff) | |
KVM: x86: Don't re-acquire SRCU lock in complete_emulated_io()
Don't re-acquire SRCU in complete_emulated_io() now that KVM acquires the
lock in kvm_arch_vcpu_ioctl_run(). More importantly, don't overwrite
vcpu->srcu_idx. If the index acquired by complete_emulated_io() differs
from the one acquired by kvm_arch_vcpu_ioctl_run(), KVM will effectively
leak a lock and hang if/when synchronize_srcu() is invoked for the
relevant grace period.
Fixes: 8d25b7beca7e ("KVM: x86: pull kvm->srcu read-side to kvm_arch_vcpu_ioctl_run")
Cc: [email protected]
Signed-off-by: Sean Christopherson <[email protected]>
Reviewed-by: Maxim Levitsky <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strlcpy-src.c')
0 files changed, 0 insertions, 0 deletions