diff options
| author | Paolo Bonzini <[email protected]> | 2025-02-26 18:23:29 +0000 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2025-03-20 17:13:00 +0000 |
| commit | 361da275e5ce98bbab5f6990d02eb9709742d703 (patch) | |
| tree | 4c3d778f94b19cfa76eed868b60dedd6bf57a1c0 /net/unix/unix_bpf.c | |
| parent | Merge tag 'kvmarm-6.15' of https://git.kernel.org/pub/scm/linux/kernel/git/kv... (diff) | |
| parent | KVM: Drop kvm_arch_sync_events() now that all implementations are nops (diff) | |
| download | kernel-361da275e5ce98bbab5f6990d02eb9709742d703.tar.gz kernel-361da275e5ce98bbab5f6990d02eb9709742d703.zip | |
Merge branch 'kvm-nvmx-and-vm-teardown' into HEAD
The immediate issue being fixed here is a nVMX bug where KVM fails to
detect that, after nested VM-Exit, L1 has a pending IRQ (or NMI).
However, checking for a pending interrupt accesses the legacy PIC, and
x86's kvm_arch_destroy_vm() currently frees the PIC before destroying
vCPUs, i.e. checking for IRQs during the forced nested VM-Exit results
in a NULL pointer deref; that's a prerequisite for the nVMX fix.
The remaining patches attempt to bring a bit of sanity to x86's VM
teardown code, which has accumulated a lot of cruft over the years. E.g.
KVM currently unloads each vCPU's MMUs in a separate operation from
destroying vCPUs, all because when guest SMP support was added, KVM had a
kludgy MMU teardown flow that broke when a VM had more than one 1 vCPU.
And that oddity lived on, for 18 years...
Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'net/unix/unix_bpf.c')
0 files changed, 0 insertions, 0 deletions