Re: [PATCH v2 2/4] mm: vmscan: propagate real error code from per-node proactive reclaim
From: Barry Song
Date: Tue Jul 21 2026 - 03:33:50 EST
On Sat, Jul 18, 2026 at 5:54 PM Ridong Chen <ridong.chen@xxxxxxxxx> wrote:
>
> From: Ridong Chen <chenridong@xxxxxxxxxx>
>
> It has been observed that per-node proactive reclaim always returns
> -EAGAIN when any error occurs. As discussed in the mailing list [1],
> the interface should distinguish between cases where no reclaimable
> memory is left and where another entity is concurrently using the
> same interface. Propagate the real error code, consistent with how
> memcg proactive reclaim handles errors.
>
> [1] https://lore.kernel.org/all/20250717235604.2atyx2aobwowpge3@offworld/T/#m3514718be82a31b05726a49da9b61fbfc69a589e
>
> Fixes: b980077899ea ("mm: introduce per-node proactive reclaim interface")
> Reviewed-by: Muchun Song <muchun.song@xxxxxxxxx>
> Acked-by: Johannes Weiner <hannes@xxxxxxxxxxx>
> Acked-by: Shakeel Butt <shakeel.butt@xxxxxxxxx>
> Signed-off-by: Ridong Chen <chenridong@xxxxxxxxxx>
Reviewed-by: Barry Song <baohua@xxxxxxxxxx>
> ---
> mm/vmscan.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)