From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "ms@edgeless.systems" <ms@edgeless.systems>,
"kas@kernel.org" <kas@kernel.org>
Cc: "linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"Wunner, Lukas" <lukas.wunner@intel.com>,
"Hansen, Dave" <dave.hansen@intel.com>,
"ardb@kernel.org" <ardb@kernel.org>,
"Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
"Weiny, Ira" <ira.weiny@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] Fault during memory acceptance for TDX VMs with certain memory sizes
Date: Fri, 13 Feb 2026 16:53:40 +0000 [thread overview]
Message-ID: <2e77439b64b47f230e8d363a256066677cac11ef.camel@intel.com> (raw)
In-Reply-To: <aY8y6uCyejTXTejt@thinkstation>
On Fri, 2026-02-13 at 14:24 +0000, Kiryl Shutsemau wrote:
>
> I still think that we need align start/size/end to the PAGE_SIZE in
> accept_memory()/range_contains_unaccepted_memory() before doing anything
> else. Otherwise (end % unit_size) check is broken. But it seems to be
> unrelated to the problem you see.
>
> diff --git a/drivers/firmware/efi/efi.c b/drivers/firmware/efi/efi.c
> index 111e87a618e5..56e9d73412fa 100644
> --- a/drivers/firmware/efi/efi.c
> +++ b/drivers/firmware/efi/efi.c
> @@ -692,13 +692,13 @@ static __init int match_config_table(const efi_guid_t *guid,
>
> static __init void reserve_unaccepted(struct efi_unaccepted_memory *unaccepted)
> {
> - phys_addr_t start, size;
> + phys_addr_t start, end;
>
> start = PAGE_ALIGN_DOWN(efi.unaccepted);
> - size = PAGE_ALIGN(sizeof(*unaccepted) + unaccepted->size);
> + end = PAGE_ALIGN(efi.unaccepted + sizeof(*unaccepted) + unaccepted->size);
>
> - memblock_add(start, size);
> - memblock_reserve(start, size);
> + memblock_add(start, end - start);
> + memblock_reserve(start, end - start);
> }
>
> int __init efi_config_parse_tables(const efi_config_table_t *config_tables,
I was able to reproduce the original BUG on a TDX system, and after
some LLM-assisted debugging, this similar patch seems to fix it:
---
diff --git a/drivers/firmware/efi/efi.c b/drivers/firmware/efi/efi.c
index 55452e61af31d..9f66f0f535420 100644
--- a/drivers/firmware/efi/efi.c
+++ b/drivers/firmware/efi/efi.c
@@ -695,7 +695,8 @@ static __init void reserve_unaccepted(struct
efi_unaccepted_memory *unaccepted)
phys_addr_t start, size;
start = PAGE_ALIGN_DOWN(efi.unaccepted);
- size = PAGE_ALIGN(sizeof(*unaccepted) + unaccepted->size);
+ size = PAGE_ALIGN(sizeof(*unaccepted) + unaccepted->size +
+ offset_in_page(efi.unaccepted));
memblock_add(start, size);
memblock_reserve(start, size);
---
The hypothesis is that the original size calculation does not account
for the table's offset within its starting page. The EFI pool allocator
performs sub-page allocation, so efi.unaccepted may not be page
aligned.
prev parent reply other threads:[~2026-02-13 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 16:29 [BUG] Fault during memory acceptance for TDX VMs with certain memory sizes Moritz Sanft
2026-02-12 23:31 ` Dave Hansen
2026-02-13 8:34 ` Moritz Sanft
2026-02-13 11:56 ` Kiryl Shutsemau
2026-02-13 12:33 ` Moritz Sanft
2026-02-13 14:24 ` Kiryl Shutsemau
2026-02-13 14:52 ` Moritz Sanft
2026-02-13 14:52 ` Moritz Sanft
2026-02-13 16:53 ` Verma, Vishal L [this message]
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=2e77439b64b47f230e8d363a256066677cac11ef.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=ardb@kernel.org \
--cc=dave.hansen@intel.com \
--cc=ira.weiny@intel.com \
--cc=kas@kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.wunner@intel.com \
--cc=ms@edgeless.systems \
--cc=rick.p.edgecombe@intel.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