This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [MTASCsft PATCH 28/??] MT-, AS- and AC-Safety docs: manual/socket.texi
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: "Carlos O'Donell" <carlos at redhat dot com>
- Cc: codonell at redhat dot com, libc-alpha at sourceware dot org
- Date: Sat, 01 Feb 2014 01:02:48 -0200
- Subject: Re: [MTASCsft PATCH 28/??] MT-, AS- and AC-Safety docs: manual/socket.texi
- Authentication-results: sourceware.org; auth=none
- References: <ortxelb5zd dot fsf at livre dot home> <or4n4uoncj dot fsf at livre dot home> <orlhy0g5no dot fsf_-_ at livre dot home> <52EC538F dot 6090401 at redhat dot com>
On Jan 31, 2014, "Carlos O'Donell" <carlos@redhat.com> wrote:
> On 01/27/2014 10:13 PM, Alexandre Oliva wrote:
>> In this file I introduce the pattern of documenting <dataset>ent
>> functions that hold internal iteration state with @mtasurace{:<dataset>}
>> and, in addition to it, for those that use a static buffer to hold the
>> return value, @mtasurace{:<dataset>buf}.
> But a user has no idea what the `:identifier' means, it's only an
> opaque marker for similar functions with similar problems. The user
> can't infer anything from so marked functions other than they share
> the same problem so avoiding all of them avoids that particular
> problem. Right?
Yeah. And if she wants to call them anyway, it suffices to take the
measures specified under âraceâ, namely holding a separate mutex for
each named identifier, to be able to call them MT-Safely (but not
AS-Safely, for this approach may deadlock).
--
Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/ FSF Latin America board member
Free Software Evangelist Red Hat Brazil Toolchain Engineer