From: Oleg Nesterov <oleg@redhat.com>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
matt.helsley@gmail.com, davem@davemloft.net,
guillaume@morinfr.org
Subject: Re: + exitc-call-proc_exit_connector-after-exit_state-is-set.patch added to -mm tree
Date: Thu, 27 Feb 2014 20:06:26 +0100 [thread overview]
Message-ID: <20140227190626.GA6961@redhat.com> (raw)
In-Reply-To: <20140227182609.GA26307@bender.morinfr.org>
On 02/27, Guillaume Morin wrote:
>
> On 27 Feb 17:47, Oleg Nesterov wrote:
>
> > Nevermind. Please consider this trivial example:
> >
> > tfunc(void *)
> > {
> > for (;;)
> > pause();
> > }
> >
> > int main(void)
> > {
> > pthread_create(tfunc);
> > pthread_exit();
> > }
> >
> > The main thread can exit and call proc_exit_connector() before
> > register_interest_for_pid(), but WNOHANG obviously can't succeed.
>
> What matters is not the exit message of the main thread but the exit
> message from the last threaded dying. In your example, it's fine that
> waitpid fails since the process is still around. If you kill it, the
> connector will get a connector message for the thread you created in
> main().
Yes sure. But how can you know that you should take this sub-thread
into account and this is the last thread?
OK... you can probably look at every PROC_EVENT_EXIT which has the
right ->process_tgid and use wait(WNOHANG) every time to detect the
group exit.
OK, thanks, I seem to understand now. Initially I wrongly thought
that your point is literally "tgid should me reapable right after
PROC_EVENT_EXIT with this patch".
Thanks!
Oleg.
prev parent reply other threads:[~2014-02-27 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <530bbf59.78aTdR6Ql6kCpXnE%akpm@linux-foundation.org>
2014-02-25 15:10 ` + exitc-call-proc_exit_connector-after-exit_state-is-set.patch added to -mm tree Oleg Nesterov
2014-02-27 14:48 ` Guillaume Morin
2014-02-27 16:47 ` Oleg Nesterov
2014-02-27 18:26 ` Guillaume Morin
2014-02-27 19:06 ` Oleg Nesterov [this message]
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=20140227190626.GA6961@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=guillaume@morinfr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.helsley@gmail.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