From: Richard Henderson <richard.henderson@linaro.org>
To: Robbin Ehn <rehn@rivosinc.com>, qemu-devel@nongnu.org
Cc: palmer@rivosinc.com
Subject: Re: [PATCH] linux-user: Fixed cpu restore with pc 0 on SIGBUS
Date: Tue, 16 Jan 2024 09:04:02 +1100 [thread overview]
Message-ID: <c1323e2d-fa2d-4cb2-88f6-6cf80077ab70@linaro.org> (raw)
In-Reply-To: <33f27425878fb529b9e39ef22c303f6e0d90525f.camel@rivosinc.com>
On 1/13/24 07:57, Robbin Ehn wrote:
> Commit f4e1168198 (linux-user: Split out host_sig{segv,bus}_handler)
> introduced a bug, when returning from host_sigbus_handler the PC is
> never set. Thus cpu_loop_exit_restore is called with a zero PC and
> we immediate get a SIGSEGV.
>
> Signed-off-by: Robbin Ehn <rehn@rivosinc.com>
> ---
> linux-user/signal.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
Queued, thanks.
r~
prev parent reply other threads:[~2024-01-15 22:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 20:57 [PATCH] linux-user: Fixed cpu restore with pc 0 on SIGBUS Robbin Ehn
2024-01-12 21:03 ` Palmer Dabbelt
2024-01-15 7:22 ` Robbin Ehn
2024-01-15 22:04 ` 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=c1323e2d-fa2d-4cb2-88f6-6cf80077ab70@linaro.org \
--to=richard.henderson@linaro.org \
--cc=palmer@rivosinc.com \
--cc=qemu-devel@nongnu.org \
--cc=rehn@rivosinc.com \
/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).