David Hildenbrand <[email protected]> wrote: > ram_mig_ram_block_resized() will abort migration (including background > snapshots) when resizing a RAMBlock. ram_block_populate_read() will only > populate RAM up to used_length, so at least for anonymous memory > protecting everything between used_length and max_length won't > actually be protected and is just a NOP. > > So let's only protect everything up to used_length. > > Note: it still makes sense to register uffd-wp for max_length, such > that RAM_UF_WRITEPROTECT is independent of a changing used_length. > > Signed-off-by: David Hildenbrand <[email protected]>
Reviewed-by: Juan Quintela <[email protected]>
