linux-kernel - Re: [PATCH] alloc_tag: remove sysctl prefix from mem

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: <20260110181250.429195a2afa08ed61b5bbb4f@linux-foundation.org>
Date: Sat, 10 Jan 2026 18:12:50 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: ranxiaokai627@....com
Cc: surenb@...gle.com, vbabka@...e.cz, kent.overstreet@...ux.dev,
 david@...nel.org, lorenzo.stoakes@...cle.com, Liam.Howlett@...cle.com,
 rppt@...nel.org, mhocko@...e.com, corbet@....net, linux-mm@...ck.org,
 linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
 ran.xiaokai@....com.cn
Subject: Re: [PATCH] alloc_tag: remove sysctl prefix from mem_profiling boot
 parameter

On Fri,  9 Jan 2026 06:24:19 +0000 ranxiaokai627@....com wrote:

> From: Ran Xiaokai <ran.xiaokai@....com.cn>
> 
> Boot parameters prefixed with "sysctl." are processed separately
> during the final stage of system initialization via kernel_init()->
> do_sysctl_args(). Since mem_profiling support should be parsed
> in early boot stage, it is unsuitable for centralized handling
> in do_sysctl_args().
> Also, when CONFIG_MEM_ALLOC_PROFILING_DEBUG is enabled,
> the sysctl.vm.mem_profiling entry is not writable and will cause
> a warning. To prevent duplicate processing of sysctl.vm.mem_profiling,
> rename the boot parameter to "mem_profiling".

Isn't this a backwardly-incompatible change?  What happens to existing
steups which are using sysctl.vm.mem_profiling=?