linux-kernel - Re: [PATCH v3 1/1] x86/boot/compressed: Fix avoiding memmap in physical KASLR

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] [day] [month] [year] [list]

Message-ID: <CAAi7L5e6SDGhzQup_VuZBX0YaORNtwmLG6ayg6PNYEwrsOP19A@mail.gmail.com>
Date: Mon, 29 Dec 2025 15:25:12 +0100
From: Michał Cłapiński <mclapinski@...gle.com>
To: Borislav Petkov <bp@...en8.de>
Cc: Dave Hansen <dave.hansen@...el.com>, Ard Biesheuvel <ardb@...nel.org>, 
	Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, 
	Dave Hansen <dave.hansen@...ux.intel.com>, Chris Li <chrisl@...nel.org>, x86@...nel.org, 
	"H. Peter Anvin" <hpa@...or.com>, Dan Williams <dan.j.williams@...el.com>, 
	Pasha Tatashin <pasha.tatashin@...een.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/1] x86/boot/compressed: Fix avoiding memmap in
 physical KASLR

On Tue, Dec 9, 2025 at 1:44 AM Borislav Petkov <bp@...en8.de> wrote:
>
> On Mon, Dec 08, 2025 at 02:27:54PM +0100, Michał Cłapiński wrote:
> > Can we merge my solution to fix the issue sooner rather than later?
>
> We are in such a hurry and during the merge window because?

I'm sorry, I didn't realize it was the merge window. I'm new to this process.

I'm not in a hurry. What I meant is I understand that Ard's change
would also fix the issue but it's a bigger change with a higher chance
of being rolled back. That's why I believe it's a good idea to merge
my change first and then later merge Ard's change. This way, even if
it's rolled back, it won't make the bug reappear.

> Nothing's stopping you from merging your solution into your kernels in
> the meantime.

I have this solution in my kernel. I just don't want to carry it forever.

What should I do now? Should I change something in the code? Should I just wait?

Thanks for your help.