summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/sctop.py
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2026-10-09 17:49:26 +0200
committerPaolo Bonzini <pbonzini@redhat.com>2026-10-09 17:49:26 +0200
commitbb44efdb084a0fd600b64f2aaed5d932caa0c944 (patch)
tree87f0e381edf643cc2db4a37db737c7793f15f1ac /tools/perf/scripts/python/sctop.py
parenta90ee4305c4a5df72c11b31dacfdc76e00fcf78a (diff)
parentb3e6212dea2e4328a841ceb37f377583176dc735 (diff)
Merge tag 'kvm-x86-fixes-7.3-rc6' of https://github.com/kvm-x86/linux into HEAD
KVM x86 fixed for 7.3-rcN - If creating a vCPU ultimately fails, clear its entry in the AVIC Physical ID table used by hardware to perform IPI Virtualization and delivered posted IRQs. I.e. plug the same use-after-free hole related to IPI virtualization and posted IRQs that was fixed for APICv by commit b41f2ca6c0601 ("KVM: VMX: Fix stale PID-pointer table entry left after vCPU free"). - Use set_page_dirty_lock() instead of set_page_dirty() when marking a page dirty after writing back SNP firmware's desired CPUID state to userspace. Using set_page_dirty() is unsafe if the page/folio isn't locked (as pointed out by its function comment's big DANGER warning, which no one reads given the number of bugs of this exact nature). - When checking for an MMIO generation match, use the memslots for the current vCPU context (non-SMM vs. SMM), as a misbehaving guest can coerce KVM into incorrectly identifying a write as MMIO in order to bypass KVM's write-tracking.
Diffstat (limited to 'tools/perf/scripts/python/sctop.py')
0 files changed, 0 insertions, 0 deletions