mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Li Zefan <lizefan@huawei.com>, Tejun Heo <tj@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	cgroups@vger.kernel.org, containers@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org, kent.overstreet@gmail.com,
	Glauber Costa <glommer@gmail.com>,
	Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: memcg creates an unkillable task in 3.11-rc2
Date: Tue, 30 Jul 2013 14:31:20 +0200	[thread overview]
Message-ID: <20130730123120.GA15847@dhcp22.suse.cz> (raw)
In-Reply-To: <87ppu0a298.fsf_-_@tw-ebiederman.twitter.com>

On Tue 30-07-13 01:19:31, Eric W. Biederman wrote:
[...]
> Hmm. Looking farther I see what is going on. And it has nothing to do
> with the freezer. (I have commented out that code and reproduced it
> without the freezer to be doubly certain).
> 
> 
> On the exit path exit_robust_list is triggering a page fault to fault a
> page back in.  Which since we have no memory causes the exit path
> to get stuck in mem_cgroup_handle_oom.

Hmm, interesting. I assume the exit is caused by the SIGKILL, right?
If yes, then why it hasn't coughed early in __mem_cgroup_try_charge

> Which means the following change should fix the hang.  I will test it in just
> a second.
> 
> The problem is that we only handled pending fatal signals and exiting
> processes when the OOM logic was enabled. Sigh.

If this is about PF_EXITING then we should handle that earlier in the
code chain (__mem_cgroup_try_charge sounds like a proper place). Let me
think about that.

Thanks for debugging this!

> Eric
> 
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index 00a7a66..5998a57 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -1792,16 +1792,6 @@ static void mem_cgroup_out_of_memory(struct mem_cgroup *memcg, gfp_t gfp_mask,
>         unsigned int points = 0;
>         struct task_struct *chosen = NULL;
>  
> -       /*
> -        * 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
> -        * quickly exit and free its memory.
> -        */
> -       if (fatal_signal_pending(current) || current->flags & PF_EXITING) {
> -               set_thread_flag(TIF_MEMDIE);
> -               return;
> -       }
> -
>         check_panic_on_oom(CONSTRAINT_MEMCG, gfp_mask, order, NULL);
>         totalpages = mem_cgroup_get_limit(memcg) >> PAGE_SHIFT ? : 1;
>         for_each_mem_cgroup_tree(iter, memcg) {
> @@ -2220,7 +2210,15 @@ static bool mem_cgroup_handle_oom(struct mem_cgroup *memcg, gfp_t mask,
>                 mem_cgroup_oom_notify(memcg);
>         spin_unlock(&memcg_oom_lock);
>  
> -       if (need_to_kill) {
> +       /*
> +        * 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
> +        * quickly exit and free its memory.
> +        */
> +       if (fatal_signal_pending(current) || current->flags & PF_EXITING) {
> +               set_thread_flag(TIF_MEMDIE);
> +               finish_wait(&memcg_oom_waitq, &owait.wait);
> +       } else if (need_to_kill) {
>                 finish_wait(&memcg_oom_waitq, &owait.wait);
>                 mem_cgroup_out_of_memory(memcg, mask, order);
>         } else {

-- 
Michal Hocko
SUSE Labs

  reply	other threads:[~2013-07-30 12:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-23 17:47 [GIT PULL] cgroup changes for 3.11-rc2 Tejun Heo
2013-07-29  0:42 ` memcg creates an unkillable task in 3.2-rc2 Eric W. Biederman
2013-07-29  7:59   ` Michal Hocko
2013-07-29  8:54     ` Eric W. Biederman
2013-07-29  9:51       ` Michal Hocko
2013-07-29 10:21         ` Eric W. Biederman
2013-07-29 16:10         ` Tejun Heo
2013-07-29 17:03           ` Eric W. Biederman
2013-07-29 17:20             ` Tejun Heo
2013-07-29 18:06               ` Eric W. Biederman
2013-07-29 18:17               ` Michal Hocko
2013-07-29 18:13             ` Johannes Weiner
2013-07-29 18:52               ` Eric W. Biederman
2013-07-30  1:58             ` Li Zefan
2013-07-30  8:19               ` memcg creates an unkillable task in 3.11-rc2 Eric W. Biederman
2013-07-30 12:31                 ` Michal Hocko [this message]
2013-07-30 16:37                   ` Eric W. Biederman
2013-07-31  7:37                     ` Michal Hocko
2013-07-31 12:10                       ` Johannes Weiner
2013-07-31 22:09                       ` Eric W. Biederman
2013-08-01  9:06                         ` Michal Hocko
2013-09-05  9:56                           ` Michal Hocko
2013-09-06 18:09                             ` Eric W. Biederman
2013-09-09  8:31                               ` Michal Hocko
2013-07-30 16:28                 ` Eric W. Biederman
2013-09-26 23:41                   ` Fabio Kung
2013-09-27  0:35                     ` Eric W. Biederman
2013-11-12 16:00                     ` Michal Hocko

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=20130730123120.GA15847@dhcp22.suse.cz \
    --to=mhocko@suse.cz \
    --cc=cgroups@vger.kernel.org \
    --cc=containers@lists.linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=glommer@gmail.com \
    --cc=hannes@cmpxchg.org \
    --cc=kent.overstreet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®