Revision fa13843d1565d4c5b3aeb9be3343b313416bef46 authored by Paolo Bonzini on 15 October 2021, 17:05:00 UTC, committed by Paolo Bonzini on 18 October 2021, 18:07:17 UTC
If allocation of rmaps fails, but some of the pointers have already been written, those pointers can be cleaned up when the memslot is freed, or even reused later for another attempt at allocating the rmaps. Therefore there is no need to WARN, as done for example in memslot_rmap_alloc, but the allocation *must* be skipped lest KVM will overwrite the previous pointer and will indeed leak memory. Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
1 parent e2b6d94
Computing file changes ...
