linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Hillf Danton <hillf.zj@alibaba-inc.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
	Michal Hocko <mhocko@suse.cz>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org
Subject: Re: [patch v3 3/3] mm, oom: do not panic for oom kills triggered from sysrq
Date: Thu, 9 Jul 2015 14:30:47 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.10.1507091428340.17177@chino.kir.corp.google.com> (raw)
In-Reply-To: <02e601d0b9fd$d644ec50$82cec4f0$@alibaba-inc.com>

On Thu, 9 Jul 2015, Hillf Danton wrote:

> > diff --git a/Documentation/sysrq.txt b/Documentation/sysrq.txt
> > --- a/Documentation/sysrq.txt
> > +++ b/Documentation/sysrq.txt
> > @@ -75,7 +75,8 @@ On all -  write a character to /proc/sysrq-trigger.  e.g.:
> > 
> >  'e'     - Send a SIGTERM to all processes, except for init.
> > 
> > -'f'	- Will call oom_kill to kill a memory hog process.
> > +'f'	- Will call the oom killer to kill a memory hog process, but do not
> > +	  panic if nothing can be killed.
> > 
> >  'g'	- Used by kgdb (kernel debugger)
> > 
> > diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> > --- a/mm/oom_kill.c
> > +++ b/mm/oom_kill.c
> > @@ -607,6 +607,9 @@ void check_panic_on_oom(struct oom_control *oc, enum oom_constraint constraint,
> >  		if (constraint != CONSTRAINT_NONE)
> >  			return;
> >  	}
> > +	/* Do not panic for oom kills triggered by sysrq */
> > +	if (oc->order == -1)
> > +		return;
> >  	dump_header(oc, NULL, memcg);
> >  	panic("Out of memory: %s panic_on_oom is enabled\n",
> >  		sysctl_panic_on_oom == 2 ? "compulsory" : "system-wide");
> > @@ -686,11 +689,11 @@ bool out_of_memory(struct oom_control *oc)
> > 
> >  	p = select_bad_process(oc, &points, totalpages);
> >  	/* Found nothing?!?! Either we hang forever, or we panic. */
> > -	if (!p) {
> > +	if (!p && oc->order != -1) {
> >  		dump_header(oc, NULL, NULL);
> >  		panic("Out of memory and no killable processes...\n");
> >  	}
> 
> Given sysctl_panic_on_oom checked, AFAICU there seems
> no chance for panic, no matter -1 or not.
> 

I'm not sure I understand your point.

There are two oom killer panics: when panic_on_oom is enabled and when the 
oom killer can't find an eligible process.

The change to the panic_on_oom panic is dealt with in check_panic_on_oom() 
and the no eligible process panic is dealt with here.

If the sysctl is disabled, and there are no eligible processes to kill, 
the change in behavior here is that we don't panic when triggered from 
sysrq.  That's the change in the hunk above.

> > -	if (p != (void *)-1UL) {
> > +	if (p && p != (void *)-1UL) {
> >  		oom_kill_process(oc, p, points, totalpages, NULL,
> >  				 "Out of memory");
> >  		killed = 1;

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2015-07-09 21:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09  4:15 Hillf Danton
2015-07-09 21:30 ` David Rientjes [this message]
2015-07-10  7:50   ` Hillf Danton
2015-07-14 21:16     ` David Rientjes
  -- strict thread matches above, loose matches on Subject: below --
2015-06-18 23:00 [patch 1/3] mm, oom: organize oom context into struct David Rientjes
2015-07-01 21:37 ` [patch v2 " David Rientjes
2015-07-08 23:42   ` [patch v3 " David Rientjes
2015-07-08 23:42     ` [patch v3 3/3] mm, oom: do not panic for oom kills triggered from sysrq David Rientjes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.10.1507091428340.17177@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=hillf.zj@alibaba-inc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    --cc=sergey.senozhatsky.work@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox