Re: can't oom-kill zap the victim's memory?

From	Vlastimil Babka <vbabka@suse.cz>
Newsgroups	linux.kernel
Subject	Re: can't oom-kill zap the victim's memory?
Date	2015-10-07 07:20 +0200
Message-ID	<qgPiV-3yq-1@gated-at.bofh.it> (permalink)
References	(4 earlier) <qcDT3-6vz-9@gated-at.bofh.it> <qdJjH-4wk-7@gated-at.bofh.it> <qf7N0-3r7-13@gated-at.bofh.it> <qfdSp-3Vb-3@gated-at.bofh.it> <qgffs-1Q6-9@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On 5.10.2015 16:44, Michal Hocko wrote:
> So I can see basically only few ways out of this deadlock situation.
> Either we face the reality and allow small allocations (withtout
> __GFP_NOFAIL) to fail after all attempts to reclaim memory have failed
> (so after even OOM killer hasn't made any progress).

Note that small allocations already *can* fail if they are done in the context
of a task selected as OOM victim (i.e. TIF_MEMDIE). And yeah I've seen a case
when they failed in a code that "handled" the allocation failure with a
BUG_ON(!page).
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: can't oom-kill zap the victim's memory? Vlastimil Babka <vbabka@suse.cz> - 2015-10-07 07:20 +0200
  Re: can't oom-kill zap the victim's memory? Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> - 2015-10-07 12:50 +0200
    Re: can't oom-kill zap the victim's memory? Vlastimil Babka <vbabka@suse.cz> - 2015-10-08 11:50 +0200

csiph-web