From: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
To: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH] ttyname.3: Add description of the function is not thread-safe
Date: Tue, 06 Sep 2011 17:57:59 +0800 [thread overview]
Message-ID: <4E65EEA7.5060804@cn.fujitsu.com> (raw)
The function ttyname() uses a static variable "ttyname_buf", so it is not thread-safe.
Signed-off-by: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
---
man3/ttyname.3 | 11 ++++++++++-
1 files changed, 10 insertions(+), 1 deletions(-)
diff --git a/man3/ttyname.3 b/man3/ttyname.3
index 08fb2b7..5047e94 100644
--- a/man3/ttyname.3
+++ b/man3/ttyname.3
@@ -23,7 +23,7 @@
.\" Modified 2001-12-13, Martin Schulze <joey-1lCxjdRlhQ9g9hUCZPvPmw@public.gmane.org>
.\" Added ttyname_r, aeb, 2002-07-20
.\"
-.TH TTYNAME 3 2008-07-14 "Linux" "Linux Programmer's Manual"
+.TH TTYNAME 3 20011-09-06 "Linux" "Linux Programmer's Manual"
.SH NAME
ttyname, ttyname_r \- return name of a terminal
.SH SYNOPSIS
@@ -70,6 +70,15 @@ File descriptor does not refer to a terminal device.
.B ERANGE
.I buflen
was too small to allow storing the pathname.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR ttyname ()
+function is not thread-safe.
+.LP
+The
+.BR ttyname_r ()
+function is thread-safe.
.SH "CONFORMING TO"
4.2BSD, POSIX.1-2001.
.SH "SEE ALSO"
--
1.7.1
--
Best Regards,
Peng Haitao
--
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 reply other threads:[~2011-09-06 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 9:57 Peng Haitao [this message]
[not found] ` <4E65EEA7.5060804-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2013-03-17 10:50 ` [PATCH] ttyname.3: Add description of the function is not thread-safe 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=4E65EEA7.5060804@cn.fujitsu.com \
--to=penght-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