Linux Manual Pages development
 help / color / mirror / Atom feed
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] error.3: ATTRIBUTES: Note functions that are/aren't thread-safe
Date: Fri, 17 Jul 2015 11:15:19 +0800	[thread overview]
Message-ID: <1437102919.31901.6.camel@G08FNSTD140232> (raw)
In-Reply-To: <55A82A97.9020702-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

The markings match glibc markings.
markings of functions in glibc are:
- error:         MT-Safe locale
- error_at_line: MT-Unsafe race:error_at_line/error_one_per_line locale

Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
---
 man3/error.3 | 31 +++++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)

diff --git a/man3/error.3 b/man3/error.3
index 7e1d47c..7a92a76 100644
--- a/man3/error.3
+++ b/man3/error.3
@@ -118,6 +118,37 @@ is assigned the address of a function
 instead of prefixing the message with the program name and colon.
 The function should print a suitable string to
 .IR stderr .
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lb lb lbw37
+l l l.
+Interface	Attribute	Value
+T{
+.BR error ()
+T}	Thread safety	MT-Safe locale
+T{
+.BR error_at_line ()
+T}	Thread safety	T{
+MT-Unsafe race:error_at_line/error_one_per_line locale
+T}
+.TE
+
+The internal
+.I error_one_per_line
+variable is accessed (without any form of synchronization, but since
+it's an int used once, it should be safe enough) and, if
+.I error_one_per_line
+is set nonzero, the internal static variables(not exposed to users)
+used to hold the last printed file name and line number are accessed
+and modified without synchronization; the update is not atomic and it
+occurs before disabling cancellation, so it can be interrupted after
+only one of the two variables is modified. After that,
+.BR error_at_line (3)
+is very much like
+.BR error (3).
 .SH CONFORMING TO
 These functions and variables are GNU extensions, and should not be
 used in programs intended to be portable.
-- 
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

  parent reply	other threads:[~2015-07-17  3:15 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           ` Zeng Linggang [this message]
2015-07-19 20:00             ` [PATCH v2] " 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       ` [PATCH v2] " Zeng Linggang
2015-07-22 17:07         ` 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=1437102919.31901.6.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