From: Claudio Fontana <cfontana@suse.de>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Cornelia Huck" <cohuck@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Anton Johansson" <anjo@rev.ng>
Subject: Re: assert fails in s390x TCG
Date: Wed, 12 Jun 2024 15:08:40 +0200 [thread overview]
Message-ID: <1a8cd52a-6c3e-47b4-89c8-d0254ba452e7@suse.de> (raw)
In-Reply-To: <b0b49b1b-6877-487c-9f4d-b29ae54c5ab0@linaro.org>
On 6/12/24 14:41, Philippe Mathieu-Daudé wrote:
> On 28/7/23 18:43, Richard Henderson wrote:
>> On 7/28/23 09:05, Richard Henderson wrote:
>>> It's the page containing both code and a page table entry that
>>> concerns me. It seems like a kernel bug, though obviously we
>>> shouldn't crash. I'm not sure what to do about it.
>>
>> Bah. Of course it's not a kernel bug, since the store is to LowCore.
>> And of course LowCore is part of a larger page, which easily has other
>> stuff.
>
> Maybe related to
> https://lore.kernel.org/qemu-devel/20240611215814.32752-1-anjo@rev.ng/
>
Hi philippe,
this was already fixed by Ilya's commit:
commit 791b2b6a930273db694b9ba48bbb406e78715927
Author: Ilya Leoshkevich <iii@linux.ibm.com>
Date: Sat Aug 5 01:03:18 2023 +0200
target/s390x: Fix the "ignored match" case in VSTRS
Currently the emulation of VSTRS recognizes partial matches in presence
of \0 in the haystack, which, according to PoP, is not correct:
If the ZS flag is one and a zero byte was detected
in the second operand, then there can not be a
partial match ...
Add a check for this. While at it, fold a number of explicitly handled
special cases into the generic logic.
Cc: qemu-stable@nongnu.org
Reported-by: Claudio Fontana <cfontana@suse.de>
Closes: https://lists.gnu.org/archive/html/qemu-devel/2023-08/msg00633.html
Fixes: 1d706f314191 ("target/s390x: vxeh2: vector string search")
Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
Message-Id: <20230804233748.218935-3-iii@linux.ibm.com>
Tested-by: Claudio Fontana <cfontana@suse.de>
Acked-by: David Hildenbrand <david@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Ciao,
Claudio
next prev parent reply other threads:[~2024-06-12 13:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 9:08 assert fails in s390x TCG Claudio Fontana
2023-07-24 8:21 ` Claudio Fontana
2023-07-27 17:41 ` Richard Henderson
2023-07-28 13:29 ` Claudio Fontana
2023-07-28 13:33 ` Richard Henderson
2023-07-28 13:45 ` Claudio Fontana
2023-07-28 14:23 ` Claudio Fontana
2023-07-28 14:28 ` Richard Henderson
2023-07-28 14:40 ` Claudio Fontana
2023-07-28 14:46 ` Claudio Fontana
2023-07-28 16:05 ` Richard Henderson
2023-07-28 16:43 ` Richard Henderson
2024-06-12 12:41 ` Philippe Mathieu-Daudé
2024-06-12 13:08 ` Claudio Fontana [this message]
2024-06-12 14:33 ` Philippe Mathieu-Daudé
2023-07-31 11:31 ` Claudio Fontana
2023-07-31 20:51 ` Claudio Fontana
2023-08-04 9:00 ` Issue with s390 TCG and libc __strstr_arch13 [Was: Re: assert fails in s390x TCG] Claudio Fontana
2023-08-04 9:20 ` Issue with s390 TCG and libc __strstr_arch13 Thomas Huth
2023-08-04 9:58 ` Claudio Fontana
2023-08-04 14:21 ` Ilya Leoshkevich
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=1a8cd52a-6c3e-47b4-89c8-d0254ba452e7@suse.de \
--to=cfontana@suse.de \
--cc=alex.bennee@linaro.org \
--cc=anjo@rev.ng \
--cc=cohuck@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).