public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Yubin Ruan <ablacktshirt@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
	libc-alpha@sourceware.org
Subject: Re: [PATCTH 0/2] pthread_mutexattr_setrobust() and pthread_mutex_consistent()
Date: Tue, 12 Sep 2017 12:41:00 -0000	[thread overview]
Message-ID: <f56e1439-7a5f-3b7a-2ec4-0970fc6ad0ad@gmail.com> (raw)
In-Reply-To: <20170826210528.GA32472@HP.internal.baidu.com>

Hello Yubin,

[...]
> +.B PTHREAD_MUTEX_ROBUST
> +can be set on a mutex attribute object so that when the owner of the mutex
> +dies or when the process containing such a locked mutex performs
> +.IR execve (2)
> +, any future attempts to call
> +.IR pthread_mutex_lock (3)
> +on this mutex will suceed and return
> +.B EOWNERDEAD
> +to indicate that the original owner no longer exists and the mutex is left in
> +an inconsistent state. 
How did you verify the point regarding execve(2)? I don't see this
detailed mentioned in the standards or in the glibc source.

Cheers,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

  parent reply	other threads:[~2017-09-12 12:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-20  9:43 Yubin Ruan
2017-08-21  2:25 ` Yubin Ruan
2017-08-21  2:31   ` Yubin Ruan
2017-08-22  0:33 ` Michael Kerrisk (man-pages)
2017-08-22  2:19   ` Yubin Ruan
2017-08-26 14:10     ` Yubin Ruan
2017-09-11  1:50       ` Yubin Ruan
2017-09-11 20:35         ` Michael Kerrisk (man-pages)
2017-09-12 12:41       ` Michael Kerrisk (man-pages) [this message]
2017-09-13  1:39         ` Yubin Ruan
2017-09-13  4:09           ` Yubin Ruan
2017-09-13 12:28           ` Michael Kerrisk (man-pages)
2017-09-15  1:34             ` Yubin Ruan
2017-09-13 15:00       ` Michael Kerrisk (man-opages)
2017-09-15  2:49         ` Yubin Ruan
2017-09-15  7:53           ` Michael Kerrisk (man-pages)

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=f56e1439-7a5f-3b7a-2ec4-0970fc6ad0ad@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=ablacktshirt@gmail.com \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-man@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).