From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: hannes@cmpxchg.org
Cc: mhocko@kernel.org, vdavydov@virtuozzo.com, linux-mm@kvack.org
Subject: Re: [PATCH] mm: memcontrol: drop unnecessary task_will_free_mem() check.
Date: Wed, 9 Mar 2016 08:05:11 +0900 [thread overview]
Message-ID: <201603090805.FGE48462.tFJSLMOFHVOOQF@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <20160308181432.GA9091@cmpxchg.org>
Johannes Weiner wrote:
> On Wed, Mar 09, 2016 at 12:15:10AM +0900, Tetsuo Handa wrote:
> > Since mem_cgroup_out_of_memory() is called by
> > mem_cgroup_oom_synchronize(true) via pagefault_out_of_memory() via
> > page fault, and possible allocations between setting PF_EXITING and
> > calling exit_mm() are tty_audit_exit() and taskstats_exit() which will
> > not trigger page fault, task_will_free_mem(current) in
> > mem_cgroup_out_of_memory() is never true.
> >
> > Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
>
> This opens us up to subtle bugs when somebody later changes the order
> and adds new possible allocation sites between the sequence points you
> describe above, or maybe adds other mem_cgroup_out_of_memory() callers.
>
> It looks like a simplification, but it actually complicates things.
>
If currently not needed, it should be removed. This is for a clarification.
Also, what is the reason we do not need below change?
I think there is a small race window because oom_killer_disabled needs to be
checked after oom_killer_disable() held oom_lock. Is it because all userspace
processes except current are frozen before oom_killer_disable() is called and
not-yet frozen threads (i.e. kernel threads) never call mem_cgroup_out_of_memory() ?
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index ae8b81c..521cd33 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -1253,6 +1253,10 @@ static void mem_cgroup_out_of_memory(struct mem_cgroup *memcg, gfp_t gfp_mask,
mutex_lock(&oom_lock);
+ /* Check if we raced with oom_killer_disable(). */
+ if (oom_killer_disabled)
+ goto unlock;
+
/*
* If current has a pending SIGKILL or is exiting, then automatically
* select it. The goal is to allow it to allocate so that it may
--
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:[~2016-03-08 23:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 15:15 Tetsuo Handa
2016-03-08 18:14 ` Johannes Weiner
2016-03-08 23:05 ` Tetsuo Handa [this message]
2016-03-09 10:08 ` Michal Hocko
2016-03-09 10:08 ` Michal Hocko
2016-03-09 10:05 ` Michal Hocko
2016-03-10 11:15 ` Tetsuo Handa
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=201603090805.FGE48462.tFJSLMOFHVOOQF@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=vdavydov@virtuozzo.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