Re: [PATCH 03/25] mm/fbatch: temporarily disable lazyfree and mlock+munlock batching

[Vlastimil Babka (SUSE)]

On 8/24/26 15:58, Hugh Dickins wrote:
> It will not matter if we occasionally get activation or deactivation
> wrong; but a mistaken lazyfree (MADV_FREE) would likely cause dataloss.
> So disable its batching while reworking the per-cpu fbatch handling,
> then re-enable it with more thought afterwards.
> 
> Similarly disable mlock+munlock batching temporarily: they will need
> some redesign before re-enabling. Just insert one disabling line for
> now, leaving the rest of the code as it was, for consideration later.
> 
> Signed-off-by: Hugh Dickins <hughd@xxxxxxxxxx>

Reviewed-by: Vlastimil Babka (SUSE) <vbabka@xxxxxxxxxx>