All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org
Subject: Re: [PATCH 2/2] bindresvport.3: Add description of the function is thread-safe
Date: Wed, 24 Apr 2013 14:41:22 +0800	[thread overview]
Message-ID: <51777E92.506@cn.fujitsu.com> (raw)
In-Reply-To: <CAKgNAkiJBGhMTP-Vqu_cVn2kAaMhHn0AsTpYkQPFQ-zUvyLUkw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hi Michael,

On 03/17/2013 07:06 PM, Michael Kerrisk (man-pages) wrote:
> On Tue, Dec 4, 2012 at 8:55 AM, Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org> wrote:
>> The function bindresvport() uses lock to protect static variable,
>> so it is thread-safe. The patch can refer to URL:
>> http://sourceware.org/git/?p=glibc.git;a=commit;h=f6da27e53695ad1cc0e2a9490358decbbfdff5e5
> 
> Now we get to an interesting case. If I understand right,
> bindresvport() was not thread-safe, but you have now made it so,
> correct?
> 

Yes:)

> In this case, the ATTRIBUTES patch should say something like:
> 
>     Before glibc 2.??, bindresvport() was not thread-safe.
>     Since glibc 2.??, it is thread-safe.
> 
> And the changelog should include the information you gave above.
> Could you please resubmit this patch.
> 

Thanks, I will send v2 patch.


-- 
Best Regards,
Peng

> Cheers,
> 
> Michael
> 
>> Signed-off-by: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
>> ---
>>  man3/bindresvport.3 | 7 ++++++-
>>  1 file changed, 6 insertions(+), 1 deletion(-)
>>
>> diff --git a/man3/bindresvport.3 b/man3/bindresvport.3
>> index d58c33d..facc297 100644
>> --- a/man3/bindresvport.3
>> +++ b/man3/bindresvport.3
>> @@ -24,7 +24,7 @@
>>  .\" 2007-05-31, mtk: Rewrite and substantial additional text.
>>  .\" 2008-12-03, mtk: Rewrote some pieces and fixed some errors
>>  .\"
>> -.TH BINDRESVPORT 3  2008-12-03 "" "Linux Programmer's Manual"
>> +.TH BINDRESVPORT 3  2012-12-04 "" "Linux Programmer's Manual"
>>  .SH NAME
>>  bindresvport \- bind a socket to a privileged IP port
>>  .SH SYNOPSIS
>> @@ -86,6 +86,11 @@ is not NULL and
>>  .I sin->sin_family
>>  is not
>>  .BR AF_INET .
>> +.SH ATTRIBUTES
>> +.SS Multithreading (see pthreads(7))
>> +The
>> +.BR bindresvport ()
>> +function is thread-safe.
>>  .SH "CONFORMING TO"
>>  Not in POSIX.1-2001.
>>  Present on the BSDs, Solaris, and many other systems.
>> --
>> 1.8.0
>>
>> --
>> 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
> 
> 
> 

--
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:[~2013-04-24  6:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-04  7:49 [PATCH 1/2] man-pages.7: Add description of "ATTRIBUTES" Peng Haitao
     [not found] ` <1354607342-5199-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2012-12-04  7:55   ` [PATCH 2/2] bindresvport.3: Add description of the function is thread-safe Peng Haitao
     [not found]     ` <1354607730-5326-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2013-03-17 11:06       ` Michael Kerrisk (man-pages)
     [not found]         ` <CAKgNAkiJBGhMTP-Vqu_cVn2kAaMhHn0AsTpYkQPFQ-zUvyLUkw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-24  6:41           ` Peng Haitao [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=51777E92.506@cn.fujitsu.com \
    --to=penght-bthxqxjhjhxqfuhtdcdx3a@public.gmane.org \
    --cc=carlos-v2tUB8YBRSi3e3T8WW9gsA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.