All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Cc: carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org,
	aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] re_comp.3: ATTRIBUTES: Note functions that are not thread-safe
Date: Tue, 21 May 2013 13:16:21 +0200	[thread overview]
Message-ID: <519B5785.8020405@gmail.com> (raw)
In-Reply-To: <1369028212-12123-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>

On 05/20/13 07:36, Peng Haitao wrote:
> The functions re_comp() and re_exec() are not thread safe.
> 
> Signed-off-by: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>

Thanks, Peng. Applied in my local branch for this work.

Cheers,

Michael


> ---
>  man3/re_comp.3 | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/man3/re_comp.3 b/man3/re_comp.3
> index b1c3295..ca4ef64 100644
> --- a/man3/re_comp.3
> +++ b/man3/re_comp.3
> @@ -63,6 +63,13 @@ otherwise it returns a pointer to an appropriate error message.
>  
>  .BR re_exec ()
>  returns 1 for a successful match, zero for failure.
> +.SH ATTRIBUTES
> +.SS Multithreading (see pthreads(7))
> +The
> +.BR re_comp ()
> +and
> +.BR re_exec ()
> +functions are not thread-safe.
>  .SH CONFORMING TO
>  4.3BSD.
>  .SH NOTES
> 

--
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:[~2013-05-21 11:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20  5:36 [PATCH] re_comp.3: ATTRIBUTES: Note functions that are not thread-safe Peng Haitao
     [not found] ` <1369028212-12123-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2013-05-21 11:16   ` Michael Kerrisk [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=519B5785.8020405@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=penght-BthXqXjhjHXQFUHtdCDX3A@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.