linux-kernel - Re: [RFC PATCH] memory,memory_hotplug: allow restricting memory blocks to zone movable

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: <aV1pmeXP2pZ55g5i@gourry-fedora-PF4VCD3F>
Date: Tue, 6 Jan 2026 14:59:21 -0500
From: Gregory Price <gourry@...rry.net>
To: "David Hildenbrand (Red Hat)" <david@...nel.org>
Cc: hare@...e.de, linux-mm@...ck.org, linux-kernel@...r.kernel.org,
	kernel-team@...a.com, osalvador@...e.de, gregkh@...uxfoundation.org,
	rafael@...nel.org, dakr@...nel.org, akpm@...ux-foundation.org,
	lorenzo.stoakes@...cle.com, Liam.Howlett@...cle.com, vbabka@...e.cz,
	rppt@...nel.org, surenb@...gle.com, mhocko@...e.com
Subject: Re: [RFC PATCH] memory,memory_hotplug: allow restricting memory
 blocks to zone movable

On Tue, Jan 06, 2026 at 07:38:54PM +0100, David Hildenbrand (Red Hat) wrote:
> On 1/6/26 19:06, Gregory Price wrote:
> > On Tue, Jan 06, 2026 at 06:52:11PM +0100, David Hildenbrand (Red Hat) wrote:
> > > On 1/6/26 17:58, Gregory Price wrote:
> > 
> > Fair, I'll revist this once Hannes gets a chance to chime in.
> > 
> > This was effective at getting the discussion started though :P
> 
> Hehe, yes.
> 
> Another thing to look into would be to provide a way for ndctl to just
> add+online the memory in one shot, without having to go back to walking
> memory blocks to online them etc.
>

I think it's the opposite: offline+remove needing to be done in one step
while holding the hotplug lock.  Right now, I think you have to do
something like

daxctl offline-memory ...
daxctl destroy ...

You can't destroy and have it offline the memory for you in one go IIRC.

Maybe that's the ACTUAL fix here?

~Gregory