[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260115080444.GD830755@noisy.programming.kicks-ass.net>
Date: Thu, 15 Jan 2026 09:04:44 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Jonathan Cameron <jonathan.cameron@...wei.com>
Cc: Ard Biesheuvel <ardb@...nel.org>, Robert Richter <rrichter@....com>,
Alison Schofield <alison.schofield@...el.com>,
Vishal Verma <vishal.l.verma@...el.com>,
Ira Weiny <ira.weiny@...el.com>,
Dan Williams <dan.j.williams@...el.com>,
Dave Jiang <dave.jiang@...el.com>,
Davidlohr Bueso <dave@...olabs.net>, linux-cxl@...r.kernel.org,
linux-kernel@...r.kernel.org, Gregory Price <gourry@...rry.net>,
"Fabio M. De Francesco" <fabio.m.de.francesco@...ux.intel.com>,
Terry Bowman <terry.bowman@....com>,
Joshua Hahn <joshua.hahnjy@...il.com>
Subject: Re: [PATCH v9 10/13] cxl: Enable AMD Zen5 address translation using
ACPI PRMT
On Wed, Jan 14, 2026 at 06:08:59PM +0000, Jonathan Cameron wrote:
> Do we have a potential issue wrt to merging this as it stands and improving
> on it later? i.e. Is this a blocking issue for this patch set?
Well, why do you *have* to use PRMT at all? And this is a serious
question; PRMT is basically injecting unaudited magic code into the
kernel, and that is a security risk.
Worse, in order to run this shit, we have to lower or disable various
security measures.
If I had my way, we would WARN and TAINT the kernel whenever such
garbage got used.
Powered by blists - more mailing lists