summaryrefslogtreecommitdiffstats
path: root/fs/dlm
diff options
context:
space:
mode:
authorJohannes Weiner <hannes@cmpxchg.org>2013-10-16 22:47:00 +0200
committerLinus Torvalds <torvalds@linux-foundation.org>2013-10-17 06:35:53 +0200
commit84235de394d9775bfaa7fa9762a59d91fef0c1fc (patch)
treec4066a9859f12ddce7f2f4deae4efa93a2c56f52 /fs/dlm
parentmm: memcg: handle non-error OOM situations more gracefully (diff)
downloadlinux-84235de394d9775bfaa7fa9762a59d91fef0c1fc.tar.xz
linux-84235de394d9775bfaa7fa9762a59d91fef0c1fc.zip
fs: buffer: move allocation failure loop into the allocator
Buffer allocation has a very crude indefinite loop around waking the flusher threads and performing global NOFS direct reclaim because it can not handle allocation failures. The most immediate problem with this is that the allocation may fail due to a memory cgroup limit, where flushers + direct reclaim might not make any progress towards resolving the situation at all. Because unlike the global case, a memory cgroup may not have any cache at all, only anonymous pages but no swap. This situation will lead to a reclaim livelock with insane IO from waking the flushers and thrashing unrelated filesystem cache in a tight loop. Use __GFP_NOFAIL allocations for buffers for now. This makes sure that any looping happens in the page allocator, which knows how to orchestrate kswapd, direct reclaim, and the flushers sensibly. It also allows memory cgroups to detect allocations that can't handle failure and will allow them to ultimately bypass the limit if reclaim can not make progress. Reported-by: azurIt <azurit@pobox.sk> Signed-off-by: Johannes Weiner <hannes@cmpxchg.org> Cc: Michal Hocko <mhocko@suse.cz> Cc: <stable@kernel.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/dlm')
0 files changed, 0 insertions, 0 deletions