[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151002142448.GC16302@dhcp22.suse.cz>
Date: Fri, 2 Oct 2015 16:24:48 +0200
From: Michal Hocko <mhocko@...nel.org>
To: Oleg Nesterov <oleg@...hat.com>
Cc: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>,
akpm@...ux-foundation.org, rientjes@...gle.com, kwalker@...hat.com,
skozina@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH -mm v2 1/3] mm/oom_kill: remove the wrong
fatal_signal_pending() check in oom_kill_process()
On Fri 02-10-15 15:57:56, Oleg Nesterov wrote:
> On 10/02, Michal Hocko wrote:
> >
> > So clone without CLONE_THREAD should create a new thread group leader
> > and so create a new thread group.
>
> Yes.
>
> > Unless there is some other trickery
> > which I do not see right now for_each_thread from the parent task
> > shouldn't see those which are cloned without CLONE_THREAD.
>
> Yes.
>
> But I still do not understand what are you talking about, sorry ;)
yes this whole thing was off-topic and I am sorry to add more confusion
to it.
> So let me say just in case that coredump (namely zap_threads()) will
> also kill other thread groups with the same ->mm.
Yes, I wanted to make sure to clarify what the thread_group is supposed
to mean here but I only made it more confusing now that I am reading the
whole thing again. Sorry about that.
Calling processes which only share the mm as threads is confusing and
only obscures the discussion.
--
Michal Hocko
SUSE Labs
--
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