From: Richard Henderson <richard.henderson@linaro.org>
To: Szabolcs Nagy <szabolcs.nagy@arm.com>
Cc: nd@arm.com, qemu-devel@nongnu.org
Subject: Re: another tst-arm-mte bug: qemu-system segfaults
Date: Tue, 2 Jun 2020 14:58:26 -0700 [thread overview]
Message-ID: <9aa721e6-e72f-20bc-73b4-19fc3f493241@linaro.org> (raw)
In-Reply-To: <20200529120427.GB18623@arm.com>
On 5/29/20 5:04 AM, Szabolcs Nagy wrote:
> again i'm using the branch at
>
> https://github.com/rth7680/qemu/tree/tgt-arm-mte
>
> to test armv8.5-a mte, now qemu-system-aarch64 segfaults
> and it's easy to reproduce: minimal source and static
> linked binary is attached (should be executed on linux
> with mte support, i used mte-v4 kernel with reverted
> memory property check).
Now fixed on that branch.
r~
next prev parent reply other threads:[~2020-06-02 21:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 12:04 another tst-arm-mte bug: qemu-system segfaults Szabolcs Nagy
2020-06-02 21:08 ` Richard Henderson
2020-06-02 21:58 ` Richard Henderson [this message]
2020-06-03 13:50 ` Szabolcs Nagy
2020-06-03 16:21 ` Richard Henderson
2020-06-03 17:17 ` Szabolcs Nagy
2020-06-05 20:26 ` Richard Henderson
2020-06-08 15:12 ` Szabolcs Nagy
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=9aa721e6-e72f-20bc-73b4-19fc3f493241@linaro.org \
--to=richard.henderson@linaro.org \
--cc=nd@arm.com \
--cc=qemu-devel@nongnu.org \
--cc=szabolcs.nagy@arm.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).