All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ilya Leoshkevich <iii@linux.ibm.com>
To: David Hildenbrand <david@redhat.com>,
	Richard Henderson <richard.henderson@linaro.org>,
	Laurent Vivier <laurent@vivier.eu>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
	qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
	Andreas Krebbel <krebbel@linux.ibm.com>
Subject: Re: [PATCH 0/2] Fix SIGILL psw.addr reporting
Date: Fri, 21 May 2021 12:45:30 +0200	[thread overview]
Message-ID: <1e96b30913e36c289c9a8fd9a3d2564aea8e56da.camel@linux.ibm.com> (raw)
In-Reply-To: <e2eb83ba-6937-741c-ea67-1bbd2346f9d5@redhat.com>

On Fri, 2021-05-21 at 09:42 +0200, David Hildenbrand wrote:
> On 21.05.21 05:01, Ilya Leoshkevich wrote:
> > qemu-s390x puts a wrong value into SIGILL's siginfo_t's psw.addr:
> > it
> > should be a pointer to the instruction following the illegal
> > instruction, but at the moment it is a pointer to the illegal
> > instruction itself. This breaks OpenJDK, which relies on this
> > value.
> > 
> > Patch 1 fixes the issue, patch 2 adds a test.
> 
> I assume that should fix
> 
> https://bugs.launchpad.net/qemu/+bug/1920913
> 
> right?

Yes, I have this Buglink in the fix commit message.
I have to admit I did not test Java more extensively - there might be
more things going on - but at least with this the SIGILL on startup is
gone, and very simple programs work.



  reply	other threads:[~2021-05-21 10:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21  3:01 [PATCH 0/2] Fix SIGILL psw.addr reporting Ilya Leoshkevich
2021-05-21  3:01 ` [PATCH 1/2] target/s390x: " Ilya Leoshkevich
2021-05-21  7:49   ` David Hildenbrand
2021-05-21  3:01 ` [PATCH 2/2] tests/tcg/s390x: Test SIGILL handling Ilya Leoshkevich
2021-05-21  7:54   ` David Hildenbrand
2021-05-21 10:42     ` Ilya Leoshkevich
2021-05-21  3:09 ` [PATCH 0/2] Fix SIGILL psw.addr reporting no-reply
2021-05-21  7:42 ` David Hildenbrand
2021-05-21 10:45   ` Ilya Leoshkevich [this message]
2021-05-21 10:59     ` Cornelia Huck

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=1e96b30913e36c289c9a8fd9a3d2564aea8e56da.camel@linux.ibm.com \
    --to=iii@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=david@redhat.com \
    --cc=krebbel@linux.ibm.com \
    --cc=laurent@vivier.eu \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.