Re: [PATCH v10 07/18] mm: allow vma_start_read_locked/vma_start_read_locked_nested to fail

[Vlastimil Babka]

On 2/13/25 23:46, Suren Baghdasaryan wrote:
> With upcoming replacement of vm_lock with vm_refcnt, we need to handle a
> possibility of vma_start_read_locked/vma_start_read_locked_nested failing
> due to refcount overflow. Prepare for such possibility by changing these
> APIs and adjusting their users.
> 
> Signed-off-by: Suren Baghdasaryan <surenb@xxxxxxxxxx>
> Cc: Lokesh Gidra <lokeshgidra@xxxxxxxxxx>

Reviewed-by: Vlastimil Babka <vbabka@xxxxxxx>