From: Richard Henderson <richard.henderson@linaro.org>
To: Ilya Leoshkevich <iii@linux.ibm.com>,
Cornelia Huck <cohuck@redhat.com>, Thomas Huth <thuth@redhat.com>,
David Hildenbrand <david@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v2] target/s390x: Fix translation exception on illegal instruction
Date: Tue, 13 Apr 2021 17:34:09 -0700 [thread overview]
Message-ID: <a307b2e8-3afe-230f-3b5c-2076f832aadf@linaro.org> (raw)
In-Reply-To: <20210413165257.21426-1-iii@linux.ibm.com>
On 4/13/21 9:52 AM, Ilya Leoshkevich wrote:
> Hitting an uretprobe in a s390x TCG guest causes a SIGSEGV. What
> happens is:
>
> * uretprobe maps a userspace page containing an invalid instruction.
> * uretprobe replaces the target function's return address with the
> address of that page.
> * When tb_gen_code() is called on that page, tb->size ends up being 0
> (because the page starts with the invalid instruction), which causes
> virt_page2 to point to the previous page.
> * The previous page is not mapped, so this causes a spurious
> translation exception.
>
> The bug is that tb->size must never be 0: even if there is an illegal
> instruction, the instruction bytes that have been looked at must count
> towards tb->size. So adjust s390x's translate_one() to act this way
> for both illegal instructions and instructions that are known to
> generate exceptions.
>
> Also add an assertion to tb_gen_code() in order to detect such
> situations in future.
>
> Signed-off-by: Ilya Leoshkevich<iii@linux.ibm.com>
> ---
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2021-04-14 0:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 16:52 [PATCH v2] target/s390x: Fix translation exception on illegal instruction Ilya Leoshkevich
2021-04-14 0:34 ` Richard Henderson [this message]
2021-04-14 7:34 ` David Hildenbrand
2021-04-14 8:38 ` Cornelia Huck
2021-04-14 9:19 ` Ilya Leoshkevich
2021-04-14 10:27 ` Ilya Leoshkevich
2021-04-14 10:39 ` Cornelia Huck
2021-04-14 10:48 ` 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=a307b2e8-3afe-230f-3b5c-2076f832aadf@linaro.org \
--to=richard.henderson@linaro.org \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=iii@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.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).