public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Dave Young via groups.io" <dyoung=redhat.com@groups.io>
To: Usama Arif <usamaarif642@gmail.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
	linux-efi@vger.kernel.org, devel@edk2.groups.io,
	 kexec@lists.infradead.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 1/2] efi/memattr: Use desc_size instead of total size to check for corruption
Date: Wed, 22 Jan 2025 13:36:40 +0800	[thread overview]
Message-ID: <CALu+AoS5_w2CV5w+b1WrFRFH7nfwmkLZUh=AXn=D=7rAhDNVAQ@mail.gmail.com> (raw)
In-Reply-To: <c5f68f9f-1494-426b-a5b2-bf6c1483c02f@gmail.com>

Hi,
On Mon, 20 Jan 2025 at 19:48, Usama Arif <usamaarif642@gmail.com> wrote:
>
>
>
> On 20/01/2025 11:29, Ard Biesheuvel wrote:
> > On Mon, 20 Jan 2025 at 11:50, Usama Arif <usamaarif642@gmail.com> wrote:
> >>
> >>
> >>
> >> On 20/01/2025 10:32, Ard Biesheuvel wrote:
> >>> On Mon, 20 Jan 2025 at 11:27, Usama Arif <usamaarif642@gmail.com> wrote:
> >>>>
> >>>>
> >>> ...
> >>>> Hi Ard,
> >>>>
> >>>> Just wanted to check how should we proceed forward? Should we try and fix the warning
> >>>> and corruption during kexec as done in this series or not initialize memory attributes
> >>>> table at all in kexec boot? I would prefer fixing the issues as in this series.
> >>>>
> >>>
> >>> I would prefer kexec boot on x86 to disregard the memory attributes
> >>> table entirely.
> >>
> >> Would you like Dave to send something like
> >> https://lore.kernel.org/all/CALu+AoS8tb=HgaybDw5OG4A1QbOXHvuidpu0ynmz-nE1nBqzTA@mail.gmail.com/
> >> on the mailing list (wrapped in ifdef CONFIG_X86_64)
> >>
> >
> > I prefer this approach. and no need for the ifdef, this is x86
> > specific code, and the memory attributes table is already ignored
> > entirely on 32-bit x86 iirc
>
> ah yes, I ignored the file name when reviewing it and just focused on the function :)
>
> Will wait for Dave to send it.

Ok,  I will add reported-by from you and suggested-by from Ard.  But I
can not test the efi mem attr, I'd prefer to have your test results
first.  Could you confirm that?

Thanks
Dave



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121056): https://edk2.groups.io/g/devel/message/121056
Mute This Topic: https://groups.io/mt/110517813/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2025-01-28 22:07 UTC|newest]

Thread overview: 31+ 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
2025-01-20 10:27                 ` Usama Arif via groups.io
2025-01-20 10:32                   ` Ard Biesheuvel via groups.io
2025-01-20 10:50                     ` Usama Arif via groups.io
2025-01-20 11:29                       ` Ard Biesheuvel via groups.io
2025-01-20 11:48                         ` Usama Arif via groups.io
2025-01-22  5:36                           ` Dave Young via groups.io [this message]
2025-01-22 11:50                             ` Usama Arif 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

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='CALu+AoS5_w2CV5w+b1WrFRFH7nfwmkLZUh=AXn=D=7rAhDNVAQ@mail.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