| 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
| ||
|
Message-ID: <20240603072124.gagi6uxkdux2p6qa@joelS2.panther.com> Date: Mon, 3 Jun 2024 09:21:24 +0200 From: Joel Granados <j.granados@...sung.com> To: Thomas Weißschuh <thomas@...ch.de> CC: Luis Chamberlain <mcgrof@...nel.org>, <linux-kernel@...r.kernel.org>, Kees Cook <keescook@...omium.org> Subject: Re: Current state of the sysctl constification effort On Fri, May 31, 2024 at 12:50:32PM +0200, Thomas Weißschuh wrote: > 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. Indeed. These are going to go into sysctl-next as soon as I get around to creating the branch (this week, if all goes well :) > > 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. Indeed, and I have also tested it in the kernel test bots through my kernel.org repos. So this is no surprise. > > > 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/ -- Joel Granados
Powered by blists - more mailing lists