[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230712200108.GOZK8GhJTkpuIDI4Rg@fat_crate.local>
Date: Wed, 12 Jul 2023 22:01:08 +0200
From: Borislav Petkov <bp@...en8.de>
To: Luca Boccassi <bluca@...ian.org>
Cc: Greg KH <gregkh@...uxfoundation.org>,
Daniel P. Berrangé <berrange@...hat.com>,
Emanuele Giuseppe Esposito <eesposit@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
Thomas Gleixner <tglx@...utronix.de>, lennart@...ttering.net,
Ingo Molnar <mingo@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Masahiro Yamada <masahiroy@...nel.org>,
Alexander Potapenko <glider@...gle.com>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH v2] x86/boot: add .sbat section to the bzImage
On Wed, Jul 12, 2023 at 08:56:36PM +0100, Luca Boccassi wrote:
> Everything < 3 is revoked _and_ the generation id in the stable branch
> is _not_ bumped, because it's still vulnerable and so that branch is
> effectively dead and unbootable on any system with secure boot
> enabled. This is a revocation mechanism, not a bug tracking mechanism.
> There's no mix-and-matching.
No, this is a mess waiting to happen.
> Nah, it belongs in both places. Please read the documentation and
> spend at least some time trying to understand the actual problem being
You want to have this patch in the tree - the commit message should
explain why it is needed and not point to some documentation somewhere.
> solved before commenting - or don't comment at all, that's fine too.
Here's a comment for ya:
Naked-by: Borislav Petkov (AMD) <bp@...en8.de>
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists