From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Joel Granados" <j.granados@samsung.com>,
"Luis Chamberlain" <mcgrof@kernel.org>,
"Jeff Johnson" <quic_jjohnson@quicinc.com>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Wen Yang" <wen.yang@linux.dev>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [GIT PULL] sysctl changes for v6.11-rc1
Date: Tue, 16 Jul 2024 11:13:24 -0700 [thread overview]
Message-ID: <202407161108.48DCFCD7B7@keescook> (raw)
In-Reply-To: <20240716141656.pvlrrnxziok2jwxt@joelS2.panther.com>
On Tue, Jul 16, 2024 at 04:16:56PM +0200, Joel Granados wrote:
> * Preparation patches for sysctl constification
>
> Constifying ctl_table structs prevents the modification of proc_handler
> function pointers as they would reside in .rodata. The ctl_table arguments
> in sysctl utility functions are const qualified in preparation for a future
> treewide proc_handler argument constification commit.
And to add some additional context and expectation setting, the mechanical
treewide constification pull request is planned to be sent during this
merge window once the sysctl and net trees land. Thomas Weißschuh has
it at the ready. :)
--
Kees Cook
next prev parent reply other threads:[~2024-07-16 18:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240716141703eucas1p2f6ddaf91b7363dd893d37b9aa8987dc6@eucas1p2.samsung.com>
2024-07-16 14:16 ` [GIT PULL] sysctl changes for v6.11-rc1 Joel Granados
2024-07-16 18:13 ` Kees Cook [this message]
2024-07-17 19:46 ` Joel Granados
2024-07-17 20:05 ` Thomas Weißschuh
2024-07-17 22:15 ` Kees Cook
2024-07-16 21:43 ` pr-tracker-bot
2024-08-06 18:57 ` Solar Designer
2024-08-06 19:02 ` Linus Torvalds
2024-08-06 19:24 ` Thomas Weißschuh
2024-08-13 20:52 ` 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=202407161108.48DCFCD7B7@keescook \
--to=kees@kernel.org \
--cc=j.granados@samsung.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=mcgrof@kernel.org \
--cc=quic_jjohnson@quicinc.com \
--cc=torvalds@linux-foundation.org \
--cc=wen.yang@linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).