Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Wed, 2 Aug 2023 17:55:01 +0200
From:   Borislav Petkov <bp@alien8.de>
To:     Ard Biesheuvel <ardb@kernel.org>
Cc:     linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
        Evgeniy Baskov <baskov@ispras.ru>,
        Andy Lutomirski <luto@kernel.org>,
        Dave Hansen <dave.hansen@linux.intel.com>,
        Ingo Molnar <mingo@redhat.com>,
        Peter Zijlstra <peterz@infradead.org>,
        Thomas Gleixner <tglx@linutronix.de>,
        Alexey Khoroshilov <khoroshilov@ispras.ru>,
        Peter Jones <pjones@redhat.com>,
        Gerd Hoffmann <kraxel@redhat.com>,
        Dave Young <dyoung@redhat.com>,
        Mario Limonciello <mario.limonciello@amd.com>,
        Kees Cook <keescook@chromium.org>,
        Tom Lendacky <thomas.lendacky@amd.com>,
        "Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Joerg Roedel <jroedel@suse.de>
Subject: Re: [PATCH v7 22/22] x86/efistub: Avoid legacy decompressor when
 doing EFI boot
Message-ID: <20230802155501.GDZMp8VfLCXCJog+vt@fat_crate.local>
References: <20230728090916.1538550-1-ardb@kernel.org>
 <20230728090916.1538550-23-ardb@kernel.org>
 <20230802102600.GIZMovOIUDAJAXu0F5@fat_crate.local>
 <CAMj1kXH9f+xXe3j3Bx-tku8k9eiWO_BVw70ePbfEft4stxjjgw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CAMj1kXH9f+xXe3j3Bx-tku8k9eiWO_BVw70ePbfEft4stxjjgw@mail.gmail.com>
Precedence: bulk

On Wed, Aug 02, 2023 at 12:47:24PM +0200, Ard Biesheuvel wrote:
> https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=x86-efistub-cleanup-v8
> 
> I'll prepare the v8 based on this branch after doing some more tests
> on bare metal. I'll probably send it out later today.

Thx, I'll run it here too.

> It depends on the timing. If we take the whole thing now, it should
> ideally go through -tip.

Now's fine, if it passes testing.

> There is a conflict with the kexec sev patch you just suggested on the
> list, though. I'll rebase onto that in any case, but if that causes
> any problems, we might decide to take everything except the last two
> (or three *) patches now, and defer those for later.

Right.

> * 'efi/libstub: Add limit argument to efi_random_alloc()' may conflict
> with some changes that may arrive via the RISC-V tree. That patch is
> completely independent, so perhaps I should put it on a shared stable
> branch in the EFI tree. Or alternatively, depending on how you decide
> to organize the branches, you could put it at the beginning of the
> topic branch where the RISC-V tree can merge it in.

I could simply give them the tip branch with the stuff and they can
merge it. It'll be immutable ofc.

> Or we might just ignore the conflict - it just adds a function
> argument to a function call that gets moved from one source file to
> the another in the conflicting branch, so it should be rather
> straight-forward to resolve.

That's also a possibility.

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette