Let's break the universe... for those who are willing and brave enough to run mmotm (and ideally linux-next) tree. OOM situations will lead to bugs which were hidden for years most probably but it is time we eat our own dog food and fix them up finally. The patch itself is trivial. Simply allow only one allocation retry after OOM killer has been triggered. THIS IS NOT a patch to be merged to LINUS TREE. At least not now. Signed-off-by: Michal Hocko <mhocko@xxxxxxx> --- mm/page_alloc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mm/page_alloc.c b/mm/page_alloc.c index 7ae07a5d08df..583f0f27c97e 100644 --- a/mm/page_alloc.c +++ b/mm/page_alloc.c @@ -132,7 +132,7 @@ gfp_t gfp_allowed_mask __read_mostly = GFP_BOOT_MASK; * environments are encouraged to lower the value to catch potential * issues which should be fixed. */ -unsigned long sysctl_nr_alloc_retry = ULONG_MAX; +unsigned long sysctl_nr_alloc_retry = 1; #ifdef CONFIG_PM_SLEEP /* -- 2.1.4 -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
