On Tue, Jan 27, 2026 at 01:34:31PM -0800, Andrew Morton wrote: > On Wed, 14 Jan 2026 21:42:22 -0500 Gregory Price <[email protected]> wrote: > > > Since this protection may break userspace tools, it should > > be an opt-in until those tools have time to update to the > > new daxN.M/hotplug interface instead of memory blocks. > > > > --- a/drivers/dax/Kconfig > > +++ b/drivers/dax/Kconfig > > @@ -78,4 +78,22 @@ config DEV_DAX_KMEM > > > > Say N if unsure. > > > > +config DEV_DAX_KMEM_PROTECTED > > Users must rebuild and redeploy kernels after having updated a > userspace tool. They won't thank us for this ;) > > Isn't there something we can do to make this feature > backward-compatible? >
This feature is likely getting dropped in favor of pushing such policy to a driver if it cares that much to prevent users toggling memory blocks. I will likely re-spin this series in a week or so when other non-mm changes flesh out a little clearer. This will be removed and some of the mm/memory-hotplug.c changes will be changed to prevent the modification of an already extern'd function. ~Gregory
