Hi
    We found a problem. The bottom-layer logic creates a timing thread through timer_create, but the upper-layer user is unaware of this behavior and reset the signal mask of this thread which will unmask 32 signal. As a result, the process will exit unexpectly.
    The signal 32(SIGTIMER) will only used in musl timer and block for the SIGEV_THREAD. I think it can be seen as a special internal signal like 34. But in sigprocmask and pthread_sigmask, musl lacks protection for this signal. Users can modify the shielding status of such signals. Like in android, there is a function "filter_reserved_signals" used in sigprocmask to protect the internal signals state from being modified.
    Considering that upper-layer users may not know the signal 32 has been blocked, should we add a default block for SIGTIMER in pthread_sigmask like android? Or is there other considerations?


Best
Li