On Sat, 21 Feb 2015, Johannes Weiner wrote:
> From: Johannes Weiner <hannes@xxxxxxxxxxx>
>
> mm: page_alloc: revert inadvertent !__GFP_FS retry behavior change
>
> Historically, !__GFP_FS allocations were not allowed to invoke the OOM
> killer once reclaim had failed, but nevertheless kept looping in the
> allocator. 9879de7373fc ("mm: page_alloc: embed OOM killing naturally
> into allocation slowpath"), which should have been a simple cleanup
> patch, accidentally changed the behavior to aborting the allocation at
> that point. This creates problems with filesystem callers (?) that
> currently rely on the allocator waiting for other tasks to intervene.
>
> Revert the behavior as it shouldn't have been changed as part of a
> cleanup patch.
>
> Fixes: 9879de7373fc ("mm: page_alloc: embed OOM killing naturally into allocation slowpath")
> Signed-off-by: Johannes Weiner <hannes@xxxxxxxxxxx>
Cc: stable@xxxxxxxxxxxxxxx [3.19]
Acked-by: David Rientjes <rientjes@xxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
