From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Subject: Re: [PATCH] linux-user: Move TARGET_SA_RESTORER out of generic/signal.h
Date: Sat, 15 Feb 2025 11:28:55 -0800 [thread overview]
Message-ID: <8ae3bbc8-bde8-4d92-b059-7435afaf7cd8@linaro.org> (raw)
In-Reply-To: <mvmed060xc9.fsf@suse.de>
On 2/10/25 04:59, Andreas Schwab wrote:
> SA_RESTORER and the associated sa_restorer field of struct sigaction are
> an obsolete feature, not expected to be used by future architectures.
> They are also absent on RISC-V, LoongArch, Hexagon and OpenRISC, but
> defined due to their use of generic/signal.h. This leads to corrupted
> data and out-of-bounds accesses.
>
> Move the definition of TARGET_SA_RESTORER out of generic/signal.h into the
> target_signal.h files that need it. Note that m68k has the sa_restorer
> field, but does not use it and does not define SA_RESTORER.
>
> Reported-by: Thomas Weißschuh <thomas@t-8ch.de>
> Signed-off-by: Andreas Schwab <schwab@suse.de>
> ---
> linux-user/aarch64/target_signal.h | 2 ++
> linux-user/arm/target_signal.h | 2 ++
> linux-user/generic/signal.h | 1 -
> linux-user/i386/target_signal.h | 2 ++
> linux-user/m68k/target_signal.h | 1 +
> linux-user/microblaze/target_signal.h | 2 ++
> linux-user/ppc/target_signal.h | 2 ++
> linux-user/s390x/target_signal.h | 2 ++
> linux-user/sh4/target_signal.h | 2 ++
> linux-user/x86_64/target_signal.h | 2 ++
> linux-user/xtensa/target_signal.h | 2 ++
> 11 files changed, 19 insertions(+), 1 deletion(-)
Queued, thanks.
r~
prev parent reply other threads:[~2025-02-15 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 12:59 [PATCH] linux-user: Move TARGET_SA_RESTORER out of generic/signal.h Andreas Schwab
2025-02-10 20:09 ` Richard Henderson
2025-02-12 17:56 ` Thomas Weißschuh
2025-02-15 19:28 ` Richard Henderson [this message]
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=8ae3bbc8-bde8-4d92-b059-7435afaf7cd8@linaro.org \
--to=richard.henderson@linaro.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 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).