[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.10.1502231332550.21127@chino.kir.corp.google.com>
Date: Mon, 23 Feb 2015 13:33:51 -0800 (PST)
From: David Rientjes <rientjes@...gle.com>
To: Johannes Weiner <hannes@...xchg.org>
cc: Andrew Morton <akpm@...ux-foundation.org>,
Theodore Ts'o <tytso@....edu>,
Dave Chinner <david@...morbit.com>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
mhocko@...e.cz, dchinner@...hat.com, linux-mm@...ck.org,
oleg@...hat.com, mgorman@...e.de, torvalds@...ux-foundation.org,
xfs@....sgi.com, linux-ext4@...r.kernel.org
Subject: Re: How to handle TIF_MEMDIE stalls?
On Sat, 21 Feb 2015, Johannes Weiner wrote:
> From: Johannes Weiner <hannes@...xchg.org>
>
> 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@...xchg.org>
Cc: stable@...r.kernel.org [3.19]
Acked-by: David Rientjes <rientjes@...gle.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists