Re: [PATCH 2/3] mm: vmscan: propagate real error code from per-node proactive reclaim

From: Shakeel Butt

Date: Fri Jul 17 2026 - 12:39:28 EST


On Fri, Jul 17, 2026 at 07:32:59PM +0800, Ridong 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")
> Signed-off-by: Ridong Chen <chenridong@xxxxxxxxxx>

Acked-by: Shakeel Butt <shakeel.butt@xxxxxxxxx>