linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Vince Weaver <vincent.weaver-e7X0jjDqjFGHXe+LvDLADg@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [patch v2] perf_event_open.2 : document PERF_FLAG_FD_CLOEXEC flag
Date: Thu, 10 Apr 2014 21:56:17 +0200	[thread overview]
Message-ID: <5346F761.5040705@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1404070059480.16856-6xBS8L8d439fDsnSvq7Uq4Se7xf15W0s1dQoKJhdanU@public.gmane.org>

On 04/07/2014 07:02 AM, Vince Weaver wrote:
> On Fri, 4 Apr 2014, Michael Kerrisk (man-pages) wrote:
> 
>>>>               on-exec  flags at  creation time, rather than later with
>>>>               fcntl(2), avoids potential  race  conditions  where  the
>>>>               calling  thread  invokes  perf_event_open()  at the same
>>>>               time as another thread calls fork(2) then execve(2).
>>>
>>> I'm not sure of a scuccint way to express that though.
>>
>> I think the existing text suffices.
> 
> My concern is that it should be 
>     "where the calling thread invokes *fcntl()* at the same time..."
> rather than
>     "where the calling thread invokes *perf_event_open()* at the same time..."

Fair enough. I've added the words "and fcntl(2)" after invokes  perf_event_open().

Thanks,

Michael.


> but maybe that's just a small detail, I'm fine with the current text 
> otherwise.
> 
> Vince
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
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:[~2014-04-10 19:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01 21:36 [patch v2] perf_event_open.2 : document PERF_FLAG_FD_CLOEXEC flag Vince Weaver
     [not found] ` <alpine.DEB.2.10.1404011734320.17339-6xBS8L8d439fDsnSvq7Uq4Se7xf15W0s1dQoKJhdanU@public.gmane.org>
2014-04-02  7:41   ` Michael Kerrisk (man-pages)
     [not found]     ` <533BBF1F.4070608-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-04-02 15:22       ` Vince Weaver
     [not found]         ` <alpine.DEB.2.10.1404021116290.19485-6xBS8L8d439fDsnSvq7Uq4Se7xf15W0s1dQoKJhdanU@public.gmane.org>
2014-04-04  8:17           ` Michael Kerrisk (man-pages)
     [not found]             ` <533E6A8D.3020408-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-04-07  5:02               ` Vince Weaver
     [not found]                 ` <alpine.DEB.2.10.1404070059480.16856-6xBS8L8d439fDsnSvq7Uq4Se7xf15W0s1dQoKJhdanU@public.gmane.org>
2014-04-10 19:56                   ` Michael Kerrisk (man-pages) [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=5346F761.5040705@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=vincent.weaver-e7X0jjDqjFGHXe+LvDLADg@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 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 NNTP newsgroup(s).