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

Message-ID: <20260112213929.GEaWVqEdDVwzLbk8Yf@fat_crate.local>
Date: Mon, 12 Jan 2026 22:39:29 +0100
From: Borislav Petkov <bp@...en8.de>
To: Michał Cłapiński <mclapinski@...gle.com>
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 Mon, Dec 29, 2025 at 03:25:12PM +0100, Michał Cłapiński wrote:
> 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.

Why is that so?

Ard's change is simply dropping those cmdline params which are conflicting
anyway.

So why is there even a risk to be reverted?

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

I think we should merge Ard's change directly and be done with it.

Unless I'm missing an angle...?

-- 
Regards/Gruss,
    Boris.

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