From: Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@linux.intel.com>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Dave Hansen <dave.hansen@intel.com>,
Borislav Petkov <bp@alien8.de>, Andy Lutomirski <luto@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Elena Reshetova <elena.reshetova@intel.com>,
x86@kernel.org, linux-coco@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] x86/tdx: Relax SEPT_VE_DISABLE check for debug TD
Date: Fri, 9 Dec 2022 07:45:34 -0800 [thread overview]
Message-ID: <acef3c81-635e-6753-577e-3905117823b9@linux.intel.com> (raw)
In-Reply-To: <20221209132524.20200-4-kirill.shutemov@linux.intel.com>
On 12/9/22 5:25 AM, Kirill A. Shutemov wrote:
> SEPT_VE_DISABLE check is required to keep the TD protected from VMM
> attacks, but it makes harder to debug guest kernel bugs. If guest
> touches unaccepted memory the TD will get terminated without any
> traces on what has happened.
>
> Relax the SEPT_VE_DISABLE check to warning on debug TD and panic() in
> the #VE handler on EPT-violation on private memory. It will produce
> useful backtrace.
>
> Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> ---
> arch/x86/coco/tdx/tdx.c | 14 ++++++++++++--
> 1 file changed, 12 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/coco/tdx/tdx.c b/arch/x86/coco/tdx/tdx.c
> index 8ad04d101270..0e47846ff8ff 100644
> --- a/arch/x86/coco/tdx/tdx.c
> +++ b/arch/x86/coco/tdx/tdx.c
> @@ -38,6 +38,7 @@
> #define VE_GET_PORT_NUM(e) ((e) >> 16)
> #define VE_IS_IO_STRING(e) ((e) & BIT(4))
>
> +#define ATTR_DEBUG BIT(0)
> #define ATTR_SEPT_VE_DISABLE BIT(28)
>
> /* TDX Module call error codes */
> @@ -207,8 +208,15 @@ static void tdx_parse_tdinfo(u64 *cc_mask)
> * TD-private memory. Only VMM-shared memory (MMIO) will #VE.
> */
> td_attr = out.rdx;
> - if (!(td_attr & ATTR_SEPT_VE_DISABLE))
> - tdx_panic("TD misconfiguration: SEPT_VE_DISABLE attribute must be set.");
> + if (!(td_attr & ATTR_SEPT_VE_DISABLE)) {
> + const char *msg = "TD misconfiguration: SEPT_VE_DISABLE attribute must be set.";
> +
> + /* Relax SEPT_VE_DISABLE check for debug TD. */
> + if (td_attr & ATTR_DEBUG)
> + pr_warn("%s\n", msg);
> + else
> + tdx_panic(msg);
> + }
> }
>
> /*
> @@ -682,6 +690,8 @@ static int virt_exception_kernel(struct pt_regs *regs, struct ve_info *ve)
> case EXIT_REASON_CPUID:
> return handle_cpuid(regs, ve);
> case EXIT_REASON_EPT_VIOLATION:
> + if (ve->gpa != cc_mkdec(ve->gpa))
> + panic("Unexpected EPT-violation on private memory.");
Why add this change part of TD debug check? Should this be a separate patch?
> return handle_mmio(regs, ve);
> case EXIT_REASON_IO_INSTRUCTION:
> return handle_io(regs, ve);
--
Sathyanarayanan Kuppuswamy
Linux Kernel Developer
next prev parent reply other threads:[~2022-12-09 15:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 13:25 [PATCH 0/4] x86/tdx: Changes for TDX guest initialization Kirill A. Shutemov
2022-12-09 13:25 ` [PATCH 1/4] x86/tdx: Expand __tdx_hypercall() to handle more arguments Kirill A. Shutemov
2022-12-13 22:44 ` Dave Hansen
2022-12-09 13:25 ` [PATCH 2/4] x86/tdx: Use ReportFatalError to report missing SEPT_VE_DISABLE Kirill A. Shutemov
2022-12-09 15:42 ` Sathyanarayanan Kuppuswamy
2022-12-09 17:06 ` Kirill A. Shutemov
2022-12-09 20:51 ` Sathyanarayanan Kuppuswamy
2022-12-12 16:10 ` Dave Hansen
2022-12-12 16:37 ` Sathyanarayanan Kuppuswamy
2022-12-12 16:39 ` Dave Hansen
2022-12-13 23:06 ` Dave Hansen
2022-12-15 17:12 ` Kirill A. Shutemov
2022-12-15 18:18 ` Dave Hansen
2022-12-15 18:51 ` Kirill A. Shutemov
2022-12-15 21:09 ` Dave Hansen
2022-12-16 2:38 ` Kirill A. Shutemov
2022-12-16 15:22 ` Reshetova, Elena
2022-12-09 13:25 ` [PATCH 3/4] x86/tdx: Relax SEPT_VE_DISABLE check for debug TD Kirill A. Shutemov
2022-12-09 15:45 ` Sathyanarayanan Kuppuswamy [this message]
2022-12-09 17:08 ` Kirill A. Shutemov
2022-12-13 23:13 ` Dave Hansen
2022-12-15 15:40 ` Kirill A. Shutemov
2022-12-09 13:25 ` [PATCH 4/4] x86/tdx: Disable NOTIFY_ENABLES Kirill A. Shutemov
2022-12-09 15:50 ` Sathyanarayanan Kuppuswamy
2022-12-09 17:10 ` Kirill A. Shutemov
2022-12-13 23:17 ` Dave Hansen
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=acef3c81-635e-6753-577e-3905117823b9@linux.intel.com \
--to=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=elena.reshetova@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--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