All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vegard Nossum <vegard.nossum-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Denys Vlasenko <dvlasenk-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: Quentin Casasnovas
	<quentin.casasnovas-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
	linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: ptrace.2: BUGS (missing WIFEXITED notification)
Date: Fri, 12 Aug 2016 20:37:04 +0200	[thread overview]
Message-ID: <57AE1750.50303@oracle.com> (raw)
In-Reply-To: <864524d3-6a7f-9555-b4a4-eb4816c4da18-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On 08/12/2016 06:15 PM, Denys Vlasenko wrote:
> On 08/12/2016 04:50 PM, Vegard Nossum wrote:
>   stop will happen for it (if requested), but the subsequent WIFEXITED
>   notification will not be delivered until all other threads exit.
> +(As a corollary, if the other threads in the thread group are being
> +traced, they will not exit until they have been either waited for
> +and restarted or detached, thereby blocking the exit notification
> +of the group leader to wait(2) and waitpid(2).)
>
>
> Are you trying to prevent others falling into the same trap you fell into:
> thinking that if you see PTRACE_EVENT_EXIT on a thread, it has exited?

Yes, or not exactly; more precisely, the trap we fell into was thinking
that if we see PTRACE_EVENT_EXIT, that means waitpid() will return
immediately. I know, the distinction is kind of subtle...

> I think your wording is not good at that. How about this?
>
>
>   stop will happen for it (if requested), but the subsequent WIFEXITED
>   notification will not be delivered until all other threads exit.
> +(Note that other threads, if they are traced and are in
> +PTRACE_EVENT_EXIT ptrace-stop, they did not exit yet.
> +If you assume otherwise and wait on a thread leader to exit now,
> +this may hang.
> +You need to restart or detach them for them to exit. Generally,
> +only seeing WIFEXITED or WIFSIGNALED status from the thread is
> +a definite sign that it exited).

Alright, another iteration on your version gives the following:

"""
Keep in mind that other threads in the thread group which are in a
PTRACE_EVENT_EXIT ptrace-stop have not actually exited yet. This means
that attempting to wait for the group leader with waitpid() will hang
indefinitely. In order prevent this, you must make sure that the other
threads exit properly by either restarting them or detaching from them.
In general, only WIFEXITED and WIFSIGNALED indicate that the child
has definitely exited.
"""


Vegard
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2016-08-12 18:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 14:31 ptrace.2: BUGS (missing WIFEXITED notification) Vegard Nossum
     [not found] ` <55520EAC.2010003-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2015-05-14 13:44   ` Michael Kerrisk (man-pages)
     [not found]     ` <5554A6B0.2090409-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-05-14 13:52       ` Denys Vlasenko
     [not found]         ` <5554A8A4.7060404-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-14 16:28           ` Quentin Casasnovas
     [not found]             ` <20150514162807.GA13385-Cuu6V/XUcleLI2c71l+0mdkmqwFzkYv6@public.gmane.org>
2015-05-14 16:39               ` Denys Vlasenko
     [not found]                 ` <5554CFDF.6070602-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-14 16:50                   ` Quentin Casasnovas
     [not found]                     ` <20150514165031.GB13385-Cuu6V/XUcleLI2c71l+0mdkmqwFzkYv6@public.gmane.org>
2015-05-14 17:06                       ` Denys Vlasenko
     [not found]                         ` <5554D5F8.8050305-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-14 17:41                           ` Quentin Casasnovas
2015-05-15 10:12                   ` Vegard Nossum
     [not found]                     ` <5555C69A.3070509-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2015-05-15 12:05                       ` Michael Kerrisk (man-pages)
     [not found]                         ` <CAKgNAkixHtPEdmwuVhic8k2gz8ooLmW1rJ3760oWGUC07K-5hg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-18  6:49                           ` Michael Kerrisk (man-pages)
     [not found]                             ` <55826A17.8000804-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-08-12 14:50                               ` Vegard Nossum
     [not found]                                 ` <57ADE23B.8050905-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2016-08-12 16:15                                   ` Denys Vlasenko
     [not found]                                     ` <864524d3-6a7f-9555-b4a4-eb4816c4da18-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-08-12 18:37                                       ` Vegard Nossum [this message]
     [not found]                                         ` <57AE1750.50303-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2016-08-12 19:11                                           ` Denys Vlasenko

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=57AE1750.50303@oracle.com \
    --to=vegard.nossum-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
    --cc=dvlasenk-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=quentin.casasnovas-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.