This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH 1/2] linux: Reserve a new signal for SIGTIMER
- From: Florian Weimer <fw at deneb dot enyo dot de>
- To: Adhemerval Zanella <adhemerval dot zanella at linaro dot org>
- Cc: libc-alpha at sourceware dot org
- Date: Sat, 04 Jan 2020 11:55:52 +0100
- Subject: Re: [PATCH 1/2] linux: Reserve a new signal for SIGTIMER
- References: <20191231193129.2590-1-adhemerval.zanella@linaro.org> <871rskl1uj.fsf@mid.deneb.enyo.de> <abc1c16b-8ccb-2553-5424-2ef9ddbf8433@linaro.org>
* 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).