linux-kernel - Re: [RFC 1/2] efi/memattr: Use desc_size instead of total size to check for corruption

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMj1kXFMxfOswAdBEVsCoVO90y_m1TUigWRG-3FJTsv4xOGTpw@mail.gmail.com>
Date: Mon, 20 Jan 2025 11:32:19 +0100
From: Ard Biesheuvel <ardb@...nel.org>
To: Usama Arif <usamaarif642@...il.com>
Cc: linux-efi@...r.kernel.org, devel@...2.groups.io, kexec@...ts.infradead.org, 
	hannes@...xchg.org, x86@...nel.org, linux-kernel@...r.kernel.org, 
	leitao@...ian.org, gourry@...rry.net, kernel-team@...a.com, 
	Dave Young <dyoung@...hat.com>
Subject: Re: [RFC 1/2] efi/memattr: Use desc_size instead of total size to
 check for corruption

On Mon, 20 Jan 2025 at 11:27, Usama Arif <usamaarif642@...il.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.