linux-kernel - Re: [PATCH v2 0/5] add runtime hotplug state control

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: <df04f6e2-39ee-46f0-984d-54dcba16a011@kernel.org>
Date: Thu, 15 Jan 2026 18:46:50 +0100
From: "David Hildenbrand (Red Hat)" <david@...nel.org>
To: Gregory Price <gourry@...rry.net>
Cc: linux-mm@...ck.org, linux-cxl@...r.kernel.org, nvdimm@...ts.linux.dev,
 linux-kernel@...r.kernel.org, virtualization@...ts.linux.dev,
 kernel-team@...a.com, dan.j.williams@...el.com, vishal.l.verma@...el.com,
 dave.jiang@...el.com, mst@...hat.com, jasowang@...hat.com,
 xuanzhuo@...ux.alibaba.com, eperezma@...hat.com, osalvador@...e.de,
 akpm@...ux-foundation.org
Subject: Re: [PATCH v2 0/5] add runtime hotplug state control

On 1/15/26 18:42, Gregory Price wrote:
> On Thu, Jan 15, 2026 at 06:26:21PM +0100, David Hildenbrand (Red Hat) wrote:
>> On 1/15/26 00:50, Gregory Price wrote:
>>> The dax kmem driver currently onlines memory automatically during
>>> probe using the system's default online policy but provides no way
>>> to control or query the entire region state at runtime.
>>>
>>> This series adds a sysfs interface to control DAX kmem memory
>>> hotplug state, and refactors the memory_hotplug paths to make it
>>> possible for drivers to request an online type at hotplug time.
>>
>> Gregory, slow down a bit please. I haven't even had the chance to go through
>> your replies on v1.
>>
> 
> Sorry, i realized your feedback on v1 showed there was just too much
> complexity.  I would ignore v1 entirely at this point, this version is
> significantly simpler.

Fair enough, I can see that the complexity here is likely reduced (less 
patches! ).

> 
>> I'm currently on PTO and don't have the full day to review stuff :) And boy
>> oh boy, do I have a lot of stuff in my inbox.
>>
>> Maybe given this is the second time the patch subject is suboptimal is
>> another sign to slow down a bit? :P
>>
> 
> Apologies, and I will let this one sit.

Yes, at least wait until I had the chance to reply :)

-- 
Cheers

David