This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [RFC PATCH glibc v2] pthread_setspecific: Provide signal-safety across keys
- From: Florian Weimer <fw at deneb dot enyo dot de>
- To: Carlos O'Donell <carlos at redhat dot com>
- Cc: Mathieu Desnoyers <mathieu dot desnoyers at efficios dot com>, Ben Maurer <bmaurer at fb dot com>, libc-alpha at sourceware dot org
- Date: Wed, 18 Oct 2017 07:17:56 +0200
- Subject: Re: [RFC PATCH glibc v2] pthread_setspecific: Provide signal-safety across keys
- Authentication-results: sourceware.org; auth=none
- References: <20171017232440.5134-1-mathieu.desnoyers@efficios.com> <1a8113ba-dac2-a46c-c728-d46ac2704aed@redhat.com>
* Carlos O'Donell:
> On 10/17/2017 04:24 PM, Mathieu Desnoyers wrote:
>> The intent here is to provide signal-safety against callers to
>> pthread_{get/set}specific that work on different pthread keys,
>> without hurting performance of the normal use-cases that do not
>> care about signal-safety.
>
> ...
>
> I just wanted to note 2 things before we go any further:
>
> (1) We should be able to accept your patch even though you don't
> have a copyright assignment (that I can see) with the FSF.
> The reason for this is that the patch is small and is a limited
> number of lines.
A complete patch will likely be over the threshold, though. And the
assignment is by no means a guarantee we will accept the patch, of
course.