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] getttyent.3: Add description of the functions are not thread-safe
Date: Thu, 15 Sep 2011 17:36:31 +0800 [thread overview]
Message-ID: <4E71C71F.1000400@cn.fujitsu.com> (raw)
The function getttyent() returns a pointer to the static variable, so it is not
thread-safe. The functions setttyent() and endttyent() use a static variable "tf",
so they are not thread-safe. The function getttynam() calls unsafe function
getttyent(), so it is not thread-safe.
Signed-off-by: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
---
man3/getttyent.3 | 19 ++++++++++++++++++-
1 files changed, 18 insertions(+), 1 deletions(-)
diff --git a/man3/getttyent.3 b/man3/getttyent.3
index 1cf8ebc..a4e9b17 100644
--- a/man3/getttyent.3
+++ b/man3/getttyent.3
@@ -1,7 +1,7 @@
.\" Copyright 2002 walter harms (walter.harms-jNDFPZUTrfTUvfpBxBsQfasoZZ7OtMbqG9Ur7JDdleE@public.gmane.org)
.\" Distributed under GPL
.\"
-.TH GETTTYENT 3 2002-07-18 "GNU" "Linux Programmer's Manual"
+.TH GETTTYENT 3 2011-09-15 "GNU" "Linux Programmer's Manual"
.SH NAME
getttyent, getttynam, setttyent, endttyent \- get ttys file entry
.SH SYNOPSIS
@@ -66,6 +66,23 @@ can be:
#define TTY_ON 0x01 /* enable logins (start ty_getty program) */
#define TTY_SECURE 0x02 /* allow UID 0 to login */
.fi
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR getttyent ()
+returns a pointer to the static variable, so it is not thread-safe.
+.LP
+The
+.BR setttyent ()
+and
+.BR endttyent ()
+use a static variable, so they are not thread-safe.
+.LP
+The
+.BR getttynam ()
+calls thread-unsafe function
+.BR getttyent ()
+so it is not thread-safe.
.SH "CONFORMING TO"
Not in POSIX.1-2001.
Present on the BSDs, and perhaps other systems.
--
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-15 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 9:36 Peng Haitao [this message]
[not found] ` <4E71C71F.1000400-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2013-03-17 10:59 ` [PATCH] getttyent.3: Add description of the functions are 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=4E71C71F.1000400@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