[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Wed, 28 Jul 2021 08:00:00 -0700
From: Jasper Hugunin <jasper@...unin.net>
To: musl@...ts.openwall.com
Subject: Bug in src/signal/block.c
Hello,
In musl, as far as I can tell, `_NSIG` is always defined as either 65, or
128 (for all three MIPS architectures) at the bottom of
`${arch}/bits/signal.h`. Meanwhile, in `src/signal/block.c`, there is a
test `#if ULONG_MAX == 0xffffffff && _NSIG == 129`, which will never
succeed since _NSIG will be 128 instead of 129. This seems likely to be
left over from Commit: fix _NSIG and SIGRTMAX on mips
<https://git.musl-libc.org/cgit/musl/commit/arch?id=7c440977db9444d7e6b1c3dcb1fdf4ee49ca4158>
.
I have not demonstrated the bug, I found it by inspection of the source. My
guess is that this bug causes __block_all_sigs to fail to block high real
time signals on MIPS. At best, however, this test seems to be dead code.
(I am not subscribed to the mailing list; please cc me directly on any
responses I need to see.)
My apologies if I have misunderstood the situation.
Sincerely,
- Jasper Hugunin
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.
