[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpUFBDscS2n41FdE3S016c_jkb4HaKomy14G7Ez9x4w3+g@mail.gmail.com>
Date: Thu, 16 Oct 2014 14:52:48 -0700
From: Cong Wang <xiyou.wangcong@...il.com>
To: Oleg Nesterov <oleg@...hat.com>
Cc: Michal Hocko <mhocko@...e.cz>,
David Rientjes <rientjes@...gle.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>, Tejun Heo <tj@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: + freezer-check-oom-kill-while-being-frozen.patch added to -mm tree
On Thu, Oct 16, 2014 at 2:35 PM, Oleg Nesterov <oleg@...hat.com> wrote:
>
> If a task B is already frozen, it sleeps in D state.
>
> If OOM selects B as a victim after that, it won't be woken by
> SIGKILL, thus it obviously can't call should_thaw_current() and
> notice TIF_MEMDIE.
I see your point now, it would be more clear if you can just quote
the patch instead of changelog.
So are you saying the loop in __refrigerator() is useless? Since
it will always stay in asleep after schedule()?
>
> Btw, I also do not understand the cgroup_freezing() check in
> should_thaw_current(), but this is another story.
>
I hate to repeat the previous discussion. Maybe you can just follow
the link I gave to you? :)
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists