From: "Usama Arif via groups.io" <usamaarif642=gmail.com@groups.io>
To: Dave Young <dyoung@redhat.com>
Cc: linux-efi@vger.kernel.org, devel@edk2.groups.io,
kexec@lists.infradead.org, ardb@kernel.org, hannes@cmpxchg.org,
x86@kernel.org, linux-kernel@vger.kernel.org, leitao@debian.org,
gourry@gourry.net, kernel-team@meta.com
Subject: Re: [edk2-devel] [RFC 2/2] efi/memattr: add efi_mem_attr_table as a reserved region in 820_table_firmware
Date: Fri, 10 Jan 2025 11:42:08 +0000 [thread overview]
Message-ID: <31ea58e9-147e-4c6d-861e-97f0cc7792bb@gmail.com> (raw)
In-Reply-To: <CALu+AoSg7=AJ5_x=ssznVCcssy+USHAGW_pHNpo7+_+KWRc+ag@mail.gmail.com>
On 10/01/2025 11:20, Dave Young wrote:
> On Fri, 10 Jan 2025 at 19:18, Dave Young <dyoung@redhat.com> wrote:
>>
>> On Fri, 10 Jan 2025 at 19:12, Usama Arif <usamaarif642@gmail.com> wrote:
>>>
>>>
>>>
>>> On 10/01/2025 02:50, Dave Young wrote:
>>>> Hi Usama,
>>>>
>>>> On Thu, 9 Jan 2025 at 06:00, Usama Arif <usamaarif642@gmail.com> wrote:
>>>>>
>>>>> When this area is not reserved, it comes up as usable in
>>>>> /sys/firmware/memmap. This means that kexec, which uses that memmap
>>>>> to find usable memory regions, can select the region where
>>>>> efi_mem_attr_table is and overwrite it and relocate_kernel.
>>>>
>>>> Is the attr table BOOT SERVICE DATA? If so, does efi_mem_reserve()
>>>> work for you?
>>>> Just refer to esrt.c.
>>>>
>>>
>>> Hi Dave,
>>>
>>> Its a bit difficult to reproduce the problem and therefore test the fix, but
>>> we are seeing it a lot in production. Ard proposed the same thing in
>>> https://lore.kernel.org/all/6b4780a5-ada0-405e-9f0a-4d2186177f29@gmail.com/
>>> but as I mentioned there, I dont think that efi_mem_reserve would help,
>>> as efi_mem_reserve changes e820_table, while kexec looks at
>>> /sys/firmware/memmap which uses e820_table_firmware.
>>
>> I sent a question to pm people, if the sysfs memmap comes from
>> e820_table then it will be fine. Let's see:
> s/e820_table/e820_table_kexec
>
Do you mean change /sys/firmware/memmap to point to e820_table_kexec instead
of e820_table_firmware [1]?
I thought of doing this when the first bug was encountered last year, but
didn't do it as I thought it would be frowned upon to change what sysfs file
exposes to userspace.
[1] https://elixir.bootlin.com/linux/v6.12.6/source/arch/x86/kernel/e820.c#L31
>> https://lore.kernel.org/all/CALu+AoS-nk4u=9UYP7BLS=diOxjJRf+vfv7KHXG=uXozoYazsw@mail.gmail.com/
>>
>>>
>>> Thanks,
>>> Usama
>>>
>>>> Thanks
>>>> Dave
>>>>
>>>
>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121012): https://edk2.groups.io/g/devel/message/121012
Mute This Topic: https://groups.io/mt/110518541/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2025-01-15 18:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 21:53 [edk2-devel] [RFC 0/2] efi/memattr: Fix memory corruption and warning issues Usama Arif via groups.io
2025-01-08 21:53 ` [edk2-devel] [RFC 1/2] efi/memattr: Use desc_size instead of total size to check for corruption Usama Arif via groups.io
2025-01-09 15:45 ` Ard Biesheuvel via groups.io
2025-01-09 16:36 ` Usama Arif via groups.io
2025-01-10 7:21 ` Ard Biesheuvel via groups.io
2025-01-10 10:53 ` Usama Arif via groups.io
2025-01-10 17:25 ` Ard Biesheuvel via groups.io
2025-01-13 2:33 ` Dave Young via groups.io
2025-01-13 11:27 ` Usama Arif via groups.io
2025-01-13 12:00 ` Usama Arif via groups.io
[not found] ` <ed7ad48f-2270-4966-bdba-ccd4592a0fd4@gmail.com>
2025-01-20 10:32 ` Ard Biesheuvel via groups.io
[not found] ` <029cff22-f2e0-4796-9c27-1df056e08f8f@gmail.com>
2025-01-20 11:29 ` Ard Biesheuvel via groups.io
2025-01-08 21:53 ` [edk2-devel] [RFC 2/2] efi/memattr: add efi_mem_attr_table as a reserved region in 820_table_firmware Usama Arif via groups.io
2025-01-09 16:15 ` Ard Biesheuvel via groups.io
2025-01-09 16:32 ` Usama Arif via groups.io
2025-01-09 16:47 ` Gregory Price
2025-01-10 7:32 ` Ard Biesheuvel via groups.io
2025-01-10 11:36 ` Breno Leitao
2025-01-10 17:33 ` Ard Biesheuvel via groups.io
2025-01-10 14:31 ` Usama Arif via groups.io
2025-01-10 15:50 ` Usama Arif via groups.io
2025-01-10 2:50 ` Dave Young via groups.io
2025-01-10 11:12 ` Usama Arif via groups.io
2025-01-10 11:18 ` Dave Young via groups.io
2025-01-10 11:20 ` Dave Young via groups.io
2025-01-10 11:42 ` Usama Arif via groups.io [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-list 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=31ea58e9-147e-4c6d-861e-97f0cc7792bb@gmail.com \
--to=devel@edk2.groups.io \
/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