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] getpass.3: Add description of the function is not thread-safe
Date: Tue, 06 Sep 2011 17:40:40 +0800 [thread overview]
Message-ID: <4E65EA98.6070807@cn.fujitsu.com> (raw)
The function getpass() uses a static variable "buf", so it is not thread-safe.
Signed-off-by: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
---
man3/getpass.3 | 7 ++++++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/man3/getpass.3 b/man3/getpass.3
index d363ec4..d07a323 100644
--- a/man3/getpass.3
+++ b/man3/getpass.3
@@ -20,7 +20,7 @@
.\" Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111,
.\" USA.
.\"
-.TH GETPASS 3 2010-09-20 "Linux" "Linux Programmer's Manual"
+.TH GETPASS 3 2011-09-06 "Linux" "Linux Programmer's Manual"
.SH NAME
getpass \- get a password
.SH SYNOPSIS
@@ -86,6 +86,11 @@ The process does not have a controlling terminal.
.\" A
.\" .BR getpass ()
.\" function appeared in Version 7 AT&T UNIX.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR getpass ()
+function is not thread-safe.
.SH "CONFORMING TO"
Present in SUSv2, but marked LEGACY.
Removed in POSIX.1-2001.
--
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:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 9:40 Peng Haitao [this message]
[not found] ` <4E65EA98.6070807-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2013-03-17 10:53 ` [PATCH] getpass.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=4E65EA98.6070807@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