diff options
| author | Oliver Upton <oupton@google.com> | 2021-09-16 18:15:34 +0000 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2021-10-01 03:44:47 -0400 |
| commit | 55c0cefbdbdaca7347e20a2b91320b418abc617e (patch) | |
| tree | d29e5a937cf2e583210fa2dd4a8e8c32b0b9bfaf /tools/perf/scripts/python/flamegraph.py | |
| parent | KVM: x86: extract KVM_GET_CLOCK/KVM_SET_CLOCK to separate functions (diff) | |
| download | linux-55c0cefbdbdaca7347e20a2b91320b418abc617e.tar.gz linux-55c0cefbdbdaca7347e20a2b91320b418abc617e.zip | |
KVM: x86: Fix potential race in KVM_GET_CLOCK
Sean noticed that KVM_GET_CLOCK was checking kvm_arch.use_master_clock
outside of the pvclock sync lock. This is problematic, as the clock
value written to the user may or may not actually correspond to a stable
TSC.
Fix the race by populating the entire kvm_clock_data structure behind
the pvclock_gtod_sync_lock.
Suggested-by: Sean Christopherson <seanjc@google.com>
Signed-off-by: Oliver Upton <oupton@google.com>
Message-Id: <20210916181538.968978-4-oupton@google.com>
Reviewed-by: Marcelo Tosatti <mtosatti@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions