From: Richard Henderson <richard.henderson@linaro.org>
To: "Robert R. Henry" <rrh.henry@gmail.com>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, "Robert R. Henry" <robhenry@microsoft.com>
Subject: Re: [PATCH 1/1] i386/tcg: Allow IRET from user mode to user mode for dotnet runtime
Date: Sat, 15 Jun 2024 16:25:38 -0700 [thread overview]
Message-ID: <71f86082-05df-48c8-9581-68f6417c525e@linaro.org> (raw)
In-Reply-To: <20240611162021.269457-2-robhenry@microsoft.com>
On 6/11/24 09:20, Robert R. Henry wrote:
> This fixes a bug wherein i386/tcg assumed an interrupt return using
> the IRET instruction was always returning from kernel mode to either
> kernel mode or user mode. This assumption is violated when IRET is used
> as a clever way to restore thread state, as for example in the dotnet
> runtime. There, IRET returns from user mode to user mode.
>
> This bug manifested itself as a page fault in the guest Linux kernel.
>
> This bug appears to have been in QEMU since the beginning.
>
> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/249
> Signed-off-by: Robert R. Henry <robhenry@microsoft.com>
> ---
> target/i386/tcg/seg_helper.c | 78 ++++++++++++++++++++++--------------
> 1 file changed, 47 insertions(+), 31 deletions(-)
>
> diff --git a/target/i386/tcg/seg_helper.c b/target/i386/tcg/seg_helper.c
> index 715db1f232..815d26e61d 100644
> --- a/target/i386/tcg/seg_helper.c
> +++ b/target/i386/tcg/seg_helper.c
> @@ -843,20 +843,35 @@ static void do_interrupt_protected(CPUX86State *env, int intno, int is_int,
>
> #ifdef TARGET_X86_64
>
> -#define PUSHQ_RA(sp, val, ra) \
> - { \
> - sp -= 8; \
> - cpu_stq_kernel_ra(env, sp, (val), ra); \
> - }
> -
> -#define POPQ_RA(sp, val, ra) \
> - { \
> - val = cpu_ldq_kernel_ra(env, sp, ra); \
> - sp += 8; \
> - }
> +#define PUSHQ_RA(sp, val, ra, cpl, dpl) \
> + FUNC_PUSHQ_RA(env, &sp, val, ra, cpl, dpl)
> +
> +static inline void FUNC_PUSHQ_RA(
> + CPUX86State *env, target_ulong *sp,
> + target_ulong val, target_ulong ra, int cpl, int dpl) {
> + *sp -= 8;
> + if (dpl == 0) {
> + cpu_stq_kernel_ra(env, *sp, val, ra);
> + } else {
> + cpu_stq_data_ra(env, *sp, val, ra);
> + }
> +}
This doesn't seem quite right.
I would be much happier if we were to resolve the proper mmu index earlier, once, rather
than within each call to cpu_{ld,st}*_{kernel,data}_ra. With the mmu index in hand, use
cpu_{ld,st}*_mmuidx_ra instead.
I believe you will want to factor out a subroutine of x86_cpu_mmu_index which passes in
the pl, rather than reading cpl from env->hflags. This will also allow
cpu_mmu_index_kernel to be eliminated or simplified, which is written to assume pl=0.
r~
next prev parent reply other threads:[~2024-06-15 23:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 16:20 [PATCH 0/1] i386/tcg fix for IRET as used in dotnet runtime Robert R. Henry
2024-06-11 16:20 ` [PATCH 1/1] i386/tcg: Allow IRET from user mode to user mode for " Robert R. Henry
2024-06-15 23:25 ` Richard Henderson [this message]
2024-06-16 22:44 ` Robert Henry
2024-06-17 8:33 ` Paolo Bonzini
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=71f86082-05df-48c8-9581-68f6417c525e@linaro.org \
--to=richard.henderson@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=robhenry@microsoft.com \
--cc=rrh.henry@gmail.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).