qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Helge Deller <deller@kernel.org>, qemu-devel@nongnu.org
Subject: Re: qemu-hppa-user: crashes immediately in hppa chroot
Date: Thu, 29 Aug 2024 12:38:01 +1000	[thread overview]
Message-ID: <b8fe65c4-c7ee-4f01-98df-65ff304a3eb2@linaro.org> (raw)
In-Reply-To: <Zs9am5fIuo3eXoKF@p100>

On 8/29/24 03:12, Helge Deller wrote:
> Hi Richard,
> 
> I tested qemu-user from v9.1-rc4 for hppa and noticed that it crashes
> immediately when starting a hppa chroot.
> 
> I was able to bisect the segfault back to
> commit 081a0ed188d8d9d9038f00337d331d185a7ae331
> Author: Richard Henderson <richard.henderson@linaro.org>
> Date:   Wed Mar 27 13:04:00 2024 -1000
>      target/hppa: Do not mask in copy_iaoq_entry
> 
> This commit does not apply to git head any longer, but when I instead
> apply this (modified) patch the segfault vanishes:
> 
> --- a/target/hppa/translate.c
> +++ b/target/hppa/translate.c
> @@ -664,6 +664,11 @@ static void copy_iaoq_entry(DisasContext *ctx, TCGv_i64 dest,
>                               const DisasIAQE *src)
>   {
>       tcg_gen_addi_i64(dest, src->base ? : cpu_iaoq_f, src->disp);
> +
> +#if CONFIG_USER_ONLY
> +    uint64_t mask = gva_offset_mask(ctx->tb_flags);
> +    tcg_gen_andi_i64(dest, dest, mask);
> +#endif
>   }
>   
> Any idea or suggestion to fix it?

More specifics are required.

root@stoup:/opt/chroot/hppa/sid# ./qemu-hppa -L . ./bin/echo foo
foo


r~


  reply	other threads:[~2024-08-29  2:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-28 17:12 qemu-hppa-user: crashes immediately in hppa chroot Helge Deller
2024-08-29  2:38 ` Richard Henderson [this message]
2024-08-29 14:08   ` Helge Deller

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=b8fe65c4-c7ee-4f01-98df-65ff304a3eb2@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=deller@kernel.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).