From: David Rientjes <rientjes@google.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
linux-mm@kvack.org
Subject: Re: [patch -mm 2/2] oom: use old_mm for oom_disable_count in exec
Date: Wed, 1 Sep 2010 17:50:08 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1009011748190.22920@chino.kir.corp.google.com> (raw)
In-Reply-To: <20100902092039.D05C.A69D9226@jp.fujitsu.com>
On Thu, 2 Sep 2010, KOSAKI Motohiro wrote:
> > active_mm in the exec() path can be for an unrelated thread, so the
> > oom_disable_count logic should use old_mm instead.
> >
> > Reported-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
> > Signed-off-by: David Rientjes <rientjes@google.com>
> > ---
> > fs/exec.c | 4 ++--
> > 1 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/fs/exec.c b/fs/exec.c
> > --- a/fs/exec.c
> > +++ b/fs/exec.c
> > @@ -752,8 +752,8 @@ static int exec_mmap(struct mm_struct *mm)
> > tsk->mm = mm;
> > tsk->active_mm = mm;
> > activate_mm(active_mm, mm);
> > - if (tsk->signal->oom_score_adj == OOM_SCORE_ADJ_MIN) {
> > - atomic_dec(&active_mm->oom_disable_count);
> > + if (old_mm && tsk->signal->oom_score_adj == OOM_SCORE_ADJ_MIN) {
> > + atomic_dec(&old_mm->oom_disable_count);
> > atomic_inc(&tsk->mm->oom_disable_count);
>
> Looks good. However you need to use tsk->signal->oom_adj == OOM_DISABLE because
> I removed OOM_SCORE_ADJ_MIN.
>
KOSAKI, I'm not going to argue this with you. VM patches, like where you
revert oom_score_adj, go through Andrew. That's not up for debate.
Thanks for the review.
--
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>
next prev parent reply other threads:[~2010-09-02 0:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 0:00 [patch -mm 1/2] oom: protect oom_disable_count with task_lock in fork David Rientjes
2010-09-02 0:00 ` [patch -mm 2/2] oom: use old_mm for oom_disable_count in exec David Rientjes
2010-09-02 0:25 ` KOSAKI Motohiro
2010-09-02 0:50 ` David Rientjes [this message]
2010-09-08 2:44 ` KOSAKI Motohiro
2010-09-08 3:28 ` 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.00.1009011748190.22920@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
/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