From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@intel.com, luto@kernel.org, peterz@infradead.org
Cc: ak@linux.intel.com, dan.j.williams@intel.com, david@redhat.com,
hpa@zytor.com, linux-kernel@vger.kernel.org,
sathyanarayanan.kuppuswamy@linux.intel.com, seanjc@google.com,
thomas.lendacky@amd.com, x86@kernel.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: [PATCHv2 3/3] x86/tdx: Handle load_unaligned_zeropad() page-cross to a shared page
Date: Fri, 20 May 2022 06:13:16 +0300 [thread overview]
Message-ID: <20220520031316.47722-4-kirill.shutemov@linux.intel.com> (raw)
In-Reply-To: <20220520031316.47722-1-kirill.shutemov@linux.intel.com>
load_unaligned_zeropad() can lead to unwanted loads across page boundaries.
The unwanted loads are typically harmless. But, they might be made to
totally unrelated or even unmapped memory. load_unaligned_zeropad()
relies on exception fixup (#PF, #GP and now #VE) to recover from these
unwanted loads.
In TDX guests, the second page can be shared page and VMM may configure
it to trigger #VE.
Kernel assumes that #VE on a shared page is MMIO access and tries to
decode instruction to handle it. In case of load_unaligned_zeropad() it
may result in confusion as it is not MMIO access.
Check fixup table before trying to handle MMIO.
The issue was discovered by analysis. It was not triggered during the
testing.
Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
---
arch/x86/coco/tdx/tdx.c | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/arch/x86/coco/tdx/tdx.c b/arch/x86/coco/tdx/tdx.c
index 010dc229096a..1a1c8a92cfa5 100644
--- a/arch/x86/coco/tdx/tdx.c
+++ b/arch/x86/coco/tdx/tdx.c
@@ -11,6 +11,8 @@
#include <asm/insn.h>
#include <asm/insn-eval.h>
#include <asm/pgtable.h>
+#include <asm/trapnr.h>
+#include <asm/extable.h>
/* TDX module Call Leaf IDs */
#define TDX_GET_INFO 1
@@ -299,6 +301,24 @@ static int handle_mmio(struct pt_regs *regs, struct ve_info *ve)
if (WARN_ON_ONCE(user_mode(regs)))
return -EFAULT;
+ /*
+ * load_unaligned_zeropad() relies on exception fixups in case of the
+ * word being a page-crosser and the second page is not accessible.
+ *
+ * In TDX guests, the second page can be shared page and VMM may
+ * configure it to trigger #VE.
+ *
+ * Kernel assumes that #VE on a shared page is MMIO access and tries to
+ * decode instruction to handle it. In case of load_unaligned_zeropad()
+ * it may result in confusion as it is not MMIO access.
+ *
+ * Check fixup table before trying to handle MMIO.
+ */
+ if (fixup_exception(regs, X86_TRAP_VE, 0, ve->gla)) {
+ /* regs->ip is adjusted by fixup_exception() */
+ return 0;
+ }
+
if (copy_from_kernel_nofault(buffer, (void *)regs->ip, MAX_INSN_SIZE))
return -EFAULT;
--
2.35.1
next prev parent reply other threads:[~2022-05-20 3:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 3:13 [PATCHv2 0/3] Fix for load_unaligned_zeropad() in TDX guest Kirill A. Shutemov
2022-05-20 3:13 ` [PATCHv2 1/3] x86/tdx: Fix early #VE handling Kirill A. Shutemov
2022-05-20 17:01 ` Sean Christopherson
2022-05-20 17:33 ` Sean Christopherson
2022-05-20 17:46 ` Sathyanarayanan Kuppuswamy
2022-05-20 3:13 ` [PATCHv2 2/3] x86/tdx: Clarify RIP adjustments in #VE handler Kirill A. Shutemov
2022-05-20 17:52 ` Dave Hansen
2022-05-20 18:01 ` Sean Christopherson
2022-05-20 3:13 ` Kirill A. Shutemov [this message]
2022-05-20 17:47 ` [PATCHv2 3/3] x86/tdx: Handle load_unaligned_zeropad() page-cross to a shared page Sean Christopherson
2022-05-20 18:43 ` Kirill A. Shutemov
2022-05-20 19:00 ` Sean Christopherson
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=20220520031316.47722-4-kirill.shutemov@linux.intel.com \
--to=kirill.shutemov@linux.intel.com \
--cc=ak@linux.intel.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=david@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--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
Powered by JetHome