Re: [RFC PATCH glibc v2] pthread_setspecific: Provide signal-safety across keys

[Carlos O'Donell <carlos at redhat dot com>]

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.

(2) After this patch, because submitted lines of changes are cumulative,
    we are going to need a copyright assignment to accept further changes.

You can view the project Contribution Checklist here:
https://sourceware.org/glibc/wiki/Contribution%20checklist

We'll help you work through the more esoteric aspects of the list, so
don't worry about those. However, I wanted to make the copyright aspect
as clear as possible.

It would be awesome to continue to receive contributions from someone as
experienced as yourself, particularly for parallelism and concurrency issues,
or issues that impact lttng. So if you need any help with assignments, please
feel free to email me and I can help answer any questions as a steward for
the project.

-- 
Cheers,
Carlos.