linux-kernel - Re: [PATCH v3 14/17] cxl: docs/allocation/page-allocator

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: <aCIjMNooAzKaONod@casper.infradead.org>
Date: Mon, 12 May 2025 17:34:56 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Gregory Price <gourry@...rry.net>
Cc: linux-cxl@...r.kernel.org, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org, kernel-team@...a.com,
	dave@...olabs.net, jonathan.cameron@...wei.com,
	dave.jiang@...el.com, alison.schofield@...el.com,
	vishal.l.verma@...el.com, ira.weiny@...el.com,
	dan.j.williams@...el.com, corbet@....net
Subject: Re: [PATCH v3 14/17] cxl: docs/allocation/page-allocator

On Mon, May 12, 2025 at 12:21:31PM -0400, Gregory Price wrote:
> Document some interesting interactions that occur when exposing CXL
> memory capacity to page allocator.

We should not do this.  Asking the page allocator for memory (eg for
slab) should never return memory on CXL.  There need to be special
interfaces for clients that know they can tolerate the added latency.

NAK this concept, and NAK this specific document.  I have no comment on
the previous documents.