From: Michal Hocko <mhocko@xxxxxxxx> KM_MAYFAIL didn't have any suitable GFP_FOO counterpart until recently so it relied on the default page allocator behavior for the given set of flags. This means that small allocations actually never failed. Now that we have __GFP_RETRY_HARD flags which works independently on the allocation request size we can map KM_MAYFAIL to it. The allocator will try as hard as it can to fulfill the request but fails eventually if the progress cannot be made. Signed-off-by: Michal Hocko <mhocko@xxxxxxxx> --- fs/xfs/kmem.h | 3 +++ 1 file changed, 3 insertions(+) diff --git a/fs/xfs/kmem.h b/fs/xfs/kmem.h index 689f746224e7..34e6b062ce0e 100644 --- a/fs/xfs/kmem.h +++ b/fs/xfs/kmem.h @@ -54,6 +54,9 @@ kmem_flags_convert(xfs_km_flags_t flags) lflags &= ~__GFP_FS; } + if (flags & KM_MAYFAIL) + lflags |= __GFP_RETRY_HARD; + if (flags & KM_ZERO) lflags |= __GFP_ZERO; -- 2.8.1 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>