From: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH v2] dlopen.3: ATTRIBUTES: Note functions that are thread-safe
Date: Wed, 22 Jul 2015 19:16:14 +0800 [thread overview]
Message-ID: <1437563774.7073.2.camel@G08FNSTD140232> (raw)
In-Reply-To: <55AC01D2.6050705-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
After research, We think
* dlopen(),
* dlerror(),
* dlsym(),
* dlclose(),
* dladdr(),
* dlvsym(),
* dlinfo(),
* dlmopen(),
* dladdr1()
are thread-safe. But, there are not
markings of them in glibc document.
Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
---
man3/dlopen.3 | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/man3/dlopen.3 b/man3/dlopen.3
index cb5dbf9..f8e8667 100644
--- a/man3/dlopen.3
+++ b/man3/dlopen.3
@@ -396,6 +396,29 @@ provided by glibc since version 2.1,
does the same as
.BR dlsym ()
but takes a version string as an additional argument.
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lbw30 lb lb
+l l l.
+Interface Attribute Value
+T{
+.BR dlopen (),
+.BR dlerror (),
+.BR dlsym (),
+.br
+.BR dlclose (),
+.BR dladdr (),
+.BR dlvsym (),
+.br
+.BR dlinfo (),
+.BR dlmopen (),
+.BR dladdr1 ()
+T} Thread safety MT-Safe
+.TE
+
.SH CONFORMING TO
POSIX.1-2001 describes
.BR dlclose (),
--
1.9.3
--
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
next prev parent reply other threads:[~2015-07-22 11:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 9:28 [PATCH] dlopen.3: ATTRIBUTES: Note functions that are thread-safe Zeng Linggang
[not found] ` <1435138119-30051-1-git-send-email-zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-06-24 9:28 ` [PATCH] error.3: ATTRIBUTES: Note functions that are/aren't thread-safe Zeng Linggang
[not found] ` <1435138119-30051-2-git-send-email-zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-07-16 22:05 ` Michael Kerrisk (man-pages)
[not found] ` <55A82A97.9020702-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-07-17 3:03 ` Zeng Linggang
2015-07-17 3:15 ` [PATCH v2] " Zeng Linggang
2015-07-19 20:00 ` Michael Kerrisk (man-pages)
2015-06-24 9:28 ` [PATCH] rpc.3: ATTRIBUTES: Note functions that are thread-safe Zeng Linggang
[not found] ` <1435138119-30051-3-git-send-email-zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-07-16 22:04 ` Michael Kerrisk (man-pages)
2015-06-24 9:28 ` [PATCH] xdr.3: " Zeng Linggang
[not found] ` <1435138119-30051-4-git-send-email-zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-07-16 22:04 ` Michael Kerrisk (man-pages)
2015-07-19 20:00 ` [PATCH] dlopen.3: " Michael Kerrisk (man-pages)
[not found] ` <55AC01D2.6050705-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-07-22 11:16 ` Zeng Linggang [this message]
2015-07-22 17:07 ` [PATCH v2] " 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=1437563774.7073.2.camel@G08FNSTD140232 \
--to=zenglg.jy-bthxqxjhjhxqfuhtdcdx3a@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 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).