From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Qian Lei <qianl.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
aoliva <aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
carlos <carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org>,
linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
彭海涛 <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Subject: Re: [PATCH] lockf.3: ATTRIBUTES: Note function that is thread-safe
Date: Wed, 11 Jun 2014 10:41:46 +0200 [thread overview]
Message-ID: <5398164A.3010604@gmail.com> (raw)
In-Reply-To: <1402465656.20654.9.camel@fedora>
Thanks, Qian Lei. Applied.
Cheers,
Michael
On 06/11/2014 07:47 AM, Qian Lei wrote:
> The function lockf() is thread safe.
>
> Reviewed-by: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> Signed-off-by: Qian Lei <qianl.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
> man3/lockf.3 | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/man3/lockf.3 b/man3/lockf.3
> index d33c769..8395d85 100644
> --- a/man3/lockf.3
> +++ b/man3/lockf.3
> @@ -151,6 +151,11 @@ An invalid operation was specified in
> .TP
> .B ENOLCK
> Too many segment locks open, lock table is full.
> +.SH ATTRIBUTES
> +.SS Multithreading (see pthreads(7))
> +The
> +.BR lockf ()
> +function is thread-safe.
> .SH CONFORMING TO
> SVr4, POSIX.1-2001.
> .SH SEE ALSO
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
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
prev parent reply other threads:[~2014-06-11 8:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 5:47 [PATCH] lockf.3: ATTRIBUTES: Note function that is thread-safe Qian Lei
2014-06-11 8:41 ` Michael Kerrisk (man-pages) [this message]
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=5398164A.3010604@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org \
--cc=qianl.fnst-BthXqXjhjHXQFUHtdCDX3A@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).