mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: Thorsten Glaser <tg@evolvis.org>
Cc: musl@lists.openwall.com, lihua.zhao.cn@windriver.com
Subject: Re: [musl] [PATCH] set EINVAL for sigismember when sig is invalid
Date: Tue, 29 Oct 2024 16:26:16 -0400	[thread overview]
Message-ID: <20241029202615.GC10433@brightrain.aerifal.cx> (raw)
In-Reply-To: <63e3ced1-1b7d-8427-0105-a865d21f7e6f@evolvis.org>

On Tue, Oct 29, 2024 at 02:12:49PM +0100, Thorsten Glaser wrote:
> On Tue, 29 Oct 2024, lihua.zhao.cn@windriver.com wrote:
> 
> > int sigismember(const sigset_t *set, int sig)
> > {
> > 	unsigned s = sig-1;
> >-	if (s >= _NSIG-1) return 0;
> >+	if (s < 0 || s >= _NSIG-1) {
> 
> unsigned s can never be 0, and assignment from int will wrap around,
> so the >= is enough.
> 
> There’s UB if sig == INT_MIN though.

The UB concern exists for all the existing files, so it should be
fixed there and the same idiom copied to sigismember. Note that the
above patch for sigismember does not catch signal numbers that are
invalid because they're implementation-internal, like the other sigset
functions do. That needs to be fixed, but then the internal usage in
posix_spawn would need to be fixed to match.

> 
> - 	unsigned s = sig-1;
> + 	unsigned s = sig;
> + 	++s;
> 
> Or:
> 
> - 	unsigned s = sig-1;
> + 	unsigned s = (unsigned)sig - 1U;

sig-1U is the idiomatic way we do this.

Rich

  reply	other threads:[~2024-10-29 20:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29 13:02 lihua.zhao.cn
2024-10-29 13:12 ` Thorsten Glaser
2024-10-29 20:26   ` Rich Felker [this message]
2024-10-30  3:07 ` [musl] [PATCH v2] signal: " lihua.zhao.cn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241029202615.GC10433@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=lihua.zhao.cn@windriver.com \
    --cc=musl@lists.openwall.com \
    --cc=tg@evolvis.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).