All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Michael Forney <mforney@mforney.org>, Laurent Vivier <laurent@vivier.eu>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] linux-user: Remove unnecessary static assert involving __SIGRTMAX
Date: Wed, 26 May 2021 19:16:28 +0200	[thread overview]
Message-ID: <502221eb-cc9f-ca58-2864-91aaa07006ba@amsat.org> (raw)
In-Reply-To: <20210526043928.9586-1-mforney@mforney.org>

On 5/26/21 6:39 AM, Michael Forney wrote:
> Since "linux-user: fix use of SIGRTMIN" (6bc024e7), qemu removed
> use of __SIGRTMAX except for in this QEMU_BUILD_BUG_ON assert.
> Presumably, this check is to ensure that the loop in signal_table_init
> from SIGRTMIN to SIGRTMAX falls within the bounds of
> host_to_target_signal_table (_NSIG).
> 
> However, _NSIG is already defined to be the one larger than the
> largest signal supported by the system (as specified in the upcoming
> POSIX revision[0]), so the check is unnecessary.
> 
> musl libc does not define __SIGRTMAX, so removing this check fixes
> one of the last remaining errors when building qemu.
> 
> [0] https://www.austingroupbugs.net/view.php?id=741
> 
> Signed-off-by: Michael Forney <mforney@mforney.org>
> ---
> If you prefer, I can send an alternate patch to leave the
> QEMU_BUILD_BUG_ON, but guard it by #ifdef __SIGRTMAX.

This looks safer, personally I prefer, but let's see what the
maintainers prefer.

>  linux-user/signal.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/linux-user/signal.c b/linux-user/signal.c
> index 9016896dcd..6f62f2b528 100644
> --- a/linux-user/signal.c
> +++ b/linux-user/signal.c
> @@ -38,7 +38,6 @@ static void host_signal_handler(int host_signum, siginfo_t *info,
>   * Signal number 0 is reserved for use as kill(pid, 0), to test whether
>   * a process exists without sending it a signal.
>   */
> -QEMU_BUILD_BUG_ON(__SIGRTMAX + 1 != _NSIG);
>  static uint8_t host_to_target_signal_table[_NSIG] = {
>      [SIGHUP] = TARGET_SIGHUP,
>      [SIGINT] = TARGET_SIGINT,
> 



  reply	other threads:[~2021-05-26 17:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26  4:39 [PATCH] linux-user: Remove unnecessary static assert involving __SIGRTMAX Michael Forney
2021-05-26 17:16 ` Philippe Mathieu-Daudé [this message]
2021-05-26 18:36   ` Laurent Vivier
2021-05-26 19:02 ` [PATCH v2] linux-user: Disable static assert involving __SIGRTMAX if it is missing Michael Forney
2021-05-26 20:02   ` Laurent Vivier
2021-06-15  6:38 ` [PATCH] linux-user: Remove unnecessary static assert involving __SIGRTMAX Laurent Vivier

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=502221eb-cc9f-ca58-2864-91aaa07006ba@amsat.org \
    --to=f4bug@amsat.org \
    --cc=laurent@vivier.eu \
    --cc=mforney@mforney.org \
    --cc=qemu-devel@nongnu.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.