On Mon 11-01-16 14:07:16, Tetsuo Handa wrote: > After the OOM killer is disabled during suspend operation, > any !__GFP_NOFAIL && __GFP_FS allocations are forced to fail. > Thus, any !__GFP_NOFAIL && !__GFP_FS allocations should be > forced to fail as well. I hoped for minimum exposure of oom_killer_disabled outside of the OOM proper but this seems to be the easiest way to go. > Signed-off-by: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx> Acked-by: Michal Hocko <mhocko@xxxxxxxx> > --- > 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 3c3a5c5..214f824 100644 > --- a/mm/page_alloc.c > +++ b/mm/page_alloc.c > @@ -2766,7 +2766,7 @@ __alloc_pages_may_oom(gfp_t gfp_mask, unsigned int order, > * and the OOM killer can't be invoked, but > * keep looping as per tradition. > */ > - *did_some_progress = 1; > + *did_some_progress = !oom_killer_disabled; > goto out; > } > if (pm_suspended_storage()) > -- > 1.8.3.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> -- Michal Hocko SUSE Labs -- 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>