Received-SPF: pass (google.com: domain of linux-kernel+bounces-196696-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Date: Fri, 31 May 2024 12:50:32 +0200
From: Thomas =?utf-8?Q?Wei=C3=9Fschuh?= <thomas@t-8ch.de>
To: Joel Granados <j.granados@samsung.com>, 
	Luis Chamberlain <mcgrof@kernel.org>
Cc: linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>
Subject: Current state of the sysctl constification effort
Message-ID: <7823ff95-1490-4c1b-b489-a9c05adad645@t-8ch.de>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hi Joel, Hi Luis,

most of the sysctl handler preparation patches have been picked up by
the subsystem maintainers and are available in -next.

Only two are missing:

* utsname: constify ctl_table arguments of utility function [0]
* sysctl: constify ctl_table arguments of utility function [1]

Both of them are going through the sysctl tree anyways.

With this done it should be possible to also queue up 
sysctl: treewide: constify the ctl_table argument of handlers [2]
for the bots to chew on in -next.

My local builds are still succeeding on the last submitted version of
the patch.


Thomas

[0] https://lore.kernel.org/lkml/20240518-sysctl-const-handler-utsname-v1-1-27a6c8813620@weissschuh.net/
[1] https://lore.kernel.org/lkml/20240513-jag-constfy_sysctl_proc_args-v1-1-bba870a480d5@samsung.com/
[2] https://lore.kernel.org/lkml/20240423-sysctl-const-handler-v3-11-e0beccb836e2@weissschuh.net/