summaryrefslogtreecommitdiff
path: root/kernel/nsproxy.c
diff options
context:
space:
mode:
authorSean Christopherson <seanjc@google.com>2022-06-11 00:57:52 +0000
committerPaolo Bonzini <pbonzini@redhat.com>2022-06-20 11:49:46 -0400
commit545feb96c052809dab5ec04b95f976acca9f9364 (patch)
tree5fa98bf0e6b77569ded69b8f528c3b2b44213e9f /kernel/nsproxy.c
parent5d4283df5a0fc8299fba9443c33d219939eccc2d (diff)
downloadlwn-545feb96c052809dab5ec04b95f976acca9f9364.tar.gz
lwn-545feb96c052809dab5ec04b95f976acca9f9364.zip
Revert "KVM: x86: always allow host-initiated writes to PMU MSRs"
Revert the hack to allow host-initiated accesses to all "PMU" MSRs, as intel_is_valid_msr() returns true for _all_ MSRs, regardless of whether or not it has a snowball's chance in hell of actually being a PMU MSR. That mostly gets papered over by the actual get/set helpers only handling MSRs that they knows about, except there's the minor detail that kvm_pmu_{g,s}et_msr() eat reads and writes when the PMU is disabled. I.e. KVM will happy allow reads and writes to _any_ MSR if the PMU is disabled, either via module param or capability. This reverts commit d1c88a4020567ba4da52f778bcd9619d87e4ea75. Fixes: d1c88a402056 ("KVM: x86: always allow host-initiated writes to PMU MSRs") Signed-off-by: Sean Christopherson <seanjc@google.com> Message-Id: <20220611005755.753273-5-seanjc@google.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'kernel/nsproxy.c')
0 files changed, 0 insertions, 0 deletions