diff options
| author |   Sean Christopherson <seanjc@google.com> | 2022-04-15 00:43:41 +0000 |
|---|---|---|
| committer |   Paolo Bonzini <pbonzini@redhat.com> | 2022-04-21 13:16:10 -0400 |
| commit | 2d08935682ac5f6bfb70f7e6844ec27d4a245fa4 (patch) | |
| tree | b4c9319b2267ebb8baf7986d0a87316c27f53440 /scripts/gdb/linux/utils.py | |
| parent | Merge tag 'kvm-riscv-fixes-5.18-2' of https://github.com/kvm-riscv/linux into HEAD (diff) | |
| download | wireguard-linux-2d08935682ac5f6bfb70f7e6844ec27d4a245fa4.tar.xz wireguard-linux-2d08935682ac5f6bfb70f7e6844ec27d4a245fa4.zip | |
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: stable@vger.kernel.org
Signed-off-by: Sean Christopherson <seanjc@google.com>
Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
Message-Id: <20220415004343.2203171-2-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions