All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org,
	aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH] encrypt.3: ATTRIBUTES: Note functions that are not thread-safe
Date: Mon, 6 May 2013 16:03:25 +0800	[thread overview]
Message-ID: <1367827405-3608-1-git-send-email-penght@cn.fujitsu.com> (raw)

The functions encrypt() and setkey() are not thread safe.

Signed-off-by: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
---
 man3/encrypt.3 | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/man3/encrypt.3 b/man3/encrypt.3
index 411cb22..50b0f15 100644
--- a/man3/encrypt.3
+++ b/man3/encrypt.3
@@ -121,6 +121,19 @@ On success, it is unchanged.
 .B ENOSYS
 The function is not provided.
 (For example because of former USA export restrictions.)
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The functions
+.BR encrypt ()
+and
+.BR setkey ()
+are not thread-safe.
+.LP
+The functions
+.BR encrypt_r ()
+and
+.BR setkey_r ()
+are thread-safe.
 .SH CONFORMING TO
 The functions
 .BR encrypt ()
-- 
1.8.1.4

--
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

             reply	other threads:[~2013-05-06  8:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-06  8:03 Peng Haitao [this message]
     [not found] ` <1367827405-3608-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2013-05-18 18:07   ` [PATCH] encrypt.3: ATTRIBUTES: Note functions that are not thread-safe Michael Kerrisk

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=1367827405-3608-1-git-send-email-penght@cn.fujitsu.com \
    --to=penght-bthxqxjhjhxqfuhtdcdx3a@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=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@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.