linux-hardening - Re: [PATCH v3 00/11] sysctl: treewide: constify ctl

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20240508180003.548af21b@kernel.org>
Date: Wed, 8 May 2024 18:00:03 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Kees Cook <keescook@...omium.org>
Cc: Thomas Weißschuh <linux@...ssschuh.net>, Luis
 Chamberlain <mcgrof@...nel.org>, Joel Granados <j.granados@...sung.com>,
 Eric Dumazet <edumazet@...gle.com>, Dave Chinner <david@...morbit.com>,
 linux-fsdevel@...r.kernel.org, netdev@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org, linux-s390@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org,
 linux-mm@...ck.org, linux-security-module@...r.kernel.org,
 bpf@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
 linux-xfs@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
 linux-perf-users@...r.kernel.org, netfilter-devel@...r.kernel.org,
 coreteam@...filter.org, kexec@...ts.infradead.org,
 linux-hardening@...r.kernel.org, bridge@...ts.linux.dev,
 lvs-devel@...r.kernel.org, linux-rdma@...r.kernel.org,
 rds-devel@....oracle.com, linux-sctp@...r.kernel.org,
 linux-nfs@...r.kernel.org, apparmor@...ts.ubuntu.com
Subject: Re: [PATCH v3 00/11] sysctl: treewide: constify ctl_table argument
 of sysctl handlers

On Wed, 8 May 2024 10:11:35 -0700 Kees Cook wrote:
> > Split this per subsystem, please.  
> 
> I've done a few painful API transitions before, and I don't think the
> complexity of these changes needs a per-subsystem constification pass. I
> think this series is the right approach, but that patch 11 will need
> coordination with Linus. We regularly do system-wide prototype changes
> like this right at the end of the merge window before -rc1 comes out.

Right. I didn't read the code closely enough before responding.
Chalk my response up to being annoyed by the constant stream of
cross-tree changes in procfs without proper cover letter explaining 
how they will be merged :|