[PATCH 1/2] linux: Reserve a new signal for SIGTIMER

[Florian Weimer]

* Adhemerval Zanella:

> On 31/12/2019 16:41, Florian Weimer wrote:
>> * Adhemerval Zanella:
>> 
>>> The fix for BZ#10815 requires decouple SIGTIMER and SIGCANCEL.
>> 
>> How so?  I don't see why, sorry.
>> 
>
> Indeed 'requires' is not the right word, since I added this patch to 
> solve a different problem.  What about:

I think the premise is wrong.  Reserving another signal has backwards
compatibility implications, and we should do not so lightly.  I just
don't see the need to do this to address this bug.  There are better
ways (like the patch I posted that disables signals around the clone
call and pthread_create and automatically enables SIGCANCEL and thus
SIGTIMER on the new thread as a side effect).