Re: [PATCH] timers for kFreeBSD

[Robert Millan <rmh@debian.org>]

El 26 de març de 2012 21:29, Petr Salinger <Petr.Salinger@seznam.cz> ha escrit:
>> That sounds problematic.  Only 32 and 33 are reserved for userland. 34
>> isn't.
>
> Not really, see <bits/signum.h>
>
> [...]
> /* These are the hard limits of the kernel.  These values should not be
>   used directly at user level.  */
> #define __SIGRTMIN      65      /* be in sync with FreeBSD kernel */
> #define __SIGRTMAX      126     /* be in sync with FreeBSD kernel */

That doesn't mean the 34..64 range is reserved AFAICT.  Unless I
missed something, when someone in upstream comes up with a new signal
that has a specific meaning in the kernel, they will use 34 and our
existing binaries would break.

If we're going to abuse unreserved space, wouldn't it be safer to use
something close to __SIGRTMIN?

Besides, upstream explicitly reserves SIGTHR (32) for libpthread and
SIGLIBRT (33) for librt (for the same purpose as my patch, in fact).
Wouldn't it be less confusing if we follow upstream on this, at least
for 32 and 33?

-- 
Robert Millan