From: "Thomas Weißschuh" <thomas@t-8ch.de>
To: Joel Granados <j.granados@samsung.com>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>
Subject: Re: Current state of the sysctl constification effort
Date: Fri, 7 Jun 2024 15:54:01 +0200 [thread overview]
Message-ID: <37d5fd30-9327-4b57-8e4d-22af929d3fc4@t-8ch.de> (raw)
In-Reply-To: <20240607094053.x3cmkhmrgaw6jqd3@joelS2.panther.com>
On 2024-06-07 11:40:53+0000, Joel Granados wrote:
> 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.
> >
> > 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/
>
> All this is coming together nicely.
Indeed.
> Is there anything left to do besides
> what is being discussed in this mail, to start changing the ctl_tables
> to `static const`?
The changes to the tables also need (as per [0] and [1]):
* sysctl: move internal interfaces to const struct ctl_table
* sysctl: allow registration of const struct ctl_table
I think we do the handlers for v6.11, the rest of [0] and [1] for v6.12
and then we can go through the rest of the trees ctl_tables.
[0] https://lore.kernel.org/lkml/20231204-const-sysctl-v2-0-7a5060b11447@weissschuh.net/
[1] https://git.sr.ht/~t-8ch/linux/log/sysctl-constfy
next prev parent reply other threads:[~2024-06-07 13:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240531105042eucas1p1bcf3ee22d224c8d88aca633e5f01e0d2@eucas1p1.samsung.com>
2024-05-31 10:50 ` Thomas Weißschuh
2024-05-31 16:31 ` Kees Cook
2024-06-03 7:22 ` Joel Granados
2024-06-05 8:26 ` Joel Granados
2024-06-06 18:52 ` Kees Cook
2024-06-07 9:30 ` Joel Granados
2024-06-07 13:48 ` Thomas Weißschuh
2024-06-10 8:52 ` Joel Granados
2024-06-03 7:21 ` Joel Granados
2024-06-07 9:40 ` Joel Granados
2024-06-07 13:54 ` Thomas Weißschuh [this message]
2024-06-10 8:10 ` Joel Granados
2024-06-15 20:18 ` Thomas Weißschuh
2024-06-19 9:25 ` Joel Granados
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=37d5fd30-9327-4b57-8e4d-22af929d3fc4@t-8ch.de \
--to=thomas@t-8ch.de \
--cc=j.granados@samsung.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®