From: Miko Larsson <mikoxyzzz@gmail.com>
To: Joerg Roedel <joro@8bytes.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>
Cc: x86@kernel.org, hpa@zytor.com,
Sean Christopherson <seanjc@google.com>,
peterz@infradead.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, Joerg Roedel <jroedel@suse.de>,
Alexey Kardashevskiy <aik@amd.com>
Subject: Re: [PATCH] x86/debug: Fix stack recursion caused by DR7 accesses
Date: Mon, 30 Jan 2023 11:25:44 +0100 [thread overview]
Message-ID: <357d5157e01ee4469ca38595e941971083a51212.camel@gmail.com> (raw)
In-Reply-To: <20230130093717.460-1-joro@8bytes.org>
On Mon, 2023-01-30 at 10:37 +0100, Joerg Roedel wrote:
> From: Joerg Roedel <jroedel@suse.de>
>
> In kernels compiled with CONFIG_PARAVIRT=n the compiler re-orders the
> DR7 read in exc_nmi() to happen before the call to
> sev_es_ist_enter().
>
> This is problematic when running as an SEV-ES guest because in this
> environemnt the DR7 read might cause a #VC exception, and taking #VC
> exceptions is not safe in exc_nmi() before sev_es_ist_enter() has
> run.
>
> The result is stack recursion if the NMI was caused on the #VC IST
> stack, because a subsequent #VC exception in the NMI handler will
> overwrite the stack frame of the interrupted #VC handler.
>
> As there are no compiler barriers affecting the ordering of DR7
> reads/writes, make the accesses to this register volatile, forbidding
> the compiler to re-order them.
>
> Cc: Alexey Kardashevskiy <aik@amd.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Signed-off-by: Joerg Roedel <jroedel@suse.de>
> ---
> arch/x86/include/asm/debugreg.h | 29 +++++++++++++++++++++++++++--
> 1 file changed, 27 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/include/asm/debugreg.h
> b/arch/x86/include/asm/debugreg.h
> index b049d950612f..eb6238a5f60c 100644
> --- a/arch/x86/include/asm/debugreg.h
> +++ b/arch/x86/include/asm/debugreg.h
> @@ -39,7 +39,18 @@ static __always_inline unsigned long
> native_get_debugreg(int regno)
> asm("mov %%db6, %0" :"=r" (val));
> break;
> case 7:
> - asm("mov %%db7, %0" :"=r" (val));
> + /*
> + * Make DR7 reads volatile to forbid re-ordering them
> with other
> + * code. This is needed because a DR7 access can
> cause a #VC
> + * exception when running under SEV-ES. But taking a
> #VC
> + * exception is not safe at everywhere in the code-
> flow and
> + * re-ordering might place the access into an unsafe
> place.
> + *
> + * This happened in the NMI handler, where the DR7
> read was
> + * re-ordered to happen before the call to
> sev_es_ist_enter(),
> + * causing stack recursion.
> + */
> + asm volatile ("mov %%db7, %0" : "=r" (val));
> break;
> default:
> BUG();
> @@ -66,7 +77,21 @@ static __always_inline void
> native_set_debugreg(int regno, unsigned long value)
> asm("mov %0, %%db6" ::"r" (value));
> break;
> case 7:
> - asm("mov %0, %%db7" ::"r" (value));
> + /*
> + * Make DR7 writes volatile to forbid re-ordering
> them with
> + * other code. This is needed because a DR7 access
> can cause a
> + * #VC exception when running under SEV-ES. But
> taking a #VC
> + * exception is not safe at everywhere in the code-
> flow and
> + * re-ordering might place the access into an unsafe
> place.
> + *
> + * This happened in the NMI handler, where the DR7
> read was
> + * re-ordered to happen before the call to
> sev_es_ist_enter(),
> + * causing stack recursion.
> + *
> + * While is didn't happen with a DR7 write, add the
> volatile
> + * here too to avoid similar problems in the future.
> + */
> + asm volatile ("mov %0, %%db7" ::"r" (value));
> break;
> default:
> BUG();
This should probably be Cc'ed to the stable mailing list.
--
~miko
next prev parent reply other threads:[~2023-01-30 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 9:37 [PATCH] x86/debug: Fix stack recursion caused by DR7 accesses Joerg Roedel
2023-01-30 10:25 ` Miko Larsson [this message]
2023-01-30 10:59 ` Joerg Roedel
2023-01-30 11:44 ` David Laight
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=357d5157e01ee4469ca38595e941971083a51212.camel@gmail.com \
--to=mikoxyzzz@gmail.com \
--cc=aik@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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