[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID:
<SE1P216MB24848189A7044143E09EB84B9E362@SE1P216MB2484.KORP216.PROD.OUTLOOK.COM>
Date: Tue, 3 Dec 2024 03:06:39 +0000
From: JinCheng Li <naiveli233@...look.com>
To: musl <musl@...ts.openwall.com>
Subject: Do we need to enhance robustness in the signal mask?
Hi
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(SIGSYNCCALL).
But in sigprocmask and pthread_sigmask, musl lacks protection for these internal signals. Users can modify the shielding status of such signals which may cause problems with signal response. For example, I can cancel the masking of signal 32 for the SIGEV_THREAD, as aresult, the timing thread can exits abnormally.
But 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 internl signals such as 32 has been blocked, should we add a default block for these signals in pthread_sigmask like android to enhance the signal robustness? Or is there other considerations?
Best,
JinCheng
Content of type "text/html" skipped
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
