Re: [PATCH v5.5 29/30] KVM: Wait 'til the bitter end to initialize the "new" memslot
From: Maciej S. Szmigiero <hidden>
Date: 2021-11-11 23:53:51
Also in:
kvm, kvm-riscv, kvmarm, linux-mips, linux-riscv, lkml
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 <seanjc@google.com> ---
Reviewed-by: Maciej S. Szmigiero <redacted> _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel