Re: [PATCH v5.5 29/30] KVM: Wait 'til the bitter end to initialize the "new" memslot
"Maciej S. Szmigiero" <[email protected]>
| Newsgroups | org.kernel.vger.kvm-ppc,dev.linux.lists.kvmarm,org.infradead.lists.kvm-riscv,org.infradead.lists.linux-arm-kernel,org.infradead.lists.linux-riscv,org.kernel.vger.kvm,org.kernel.vger.linux-kernel,org.kernel.vger.linux-mips |
|---|---|
| Message-ID | <[email protected]> |
On 04.11.2021 01:25, Sean Christopherson wrote: > Initialize the "new" memslot in the !DELETE path only after the various > sanity checks have passed. This will allow a future commit to allocate > @new dynamically without having to copy a memslot, and without having to > deal with freeing @new in error paths and in the "nothing to change" path > that's hiding in the sanity checks. > > No functional change intended. > > Signed-off-by: Sean Christopherson <[email protected]> > --- Reviewed-by: Maciej S. Szmigiero <[email protected]>