From: Kees Cook <kees@kernel.org>
To: Joel Granados <j.granados@samsung.com>
Cc: "Thomas Weißschuh" <thomas@t-8ch.de>,
"Luis Chamberlain" <mcgrof@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: Current state of the sysctl constification effort
Date: Thu, 6 Jun 2024 11:52:25 -0700 [thread overview]
Message-ID: <202406061143.27C12F44A3@keescook> (raw)
In-Reply-To: <20240605082625.6hwdc3haim66rr7v@joelS2.panther.com>
On Wed, Jun 05, 2024 at 10:26:25AM +0200, Joel Granados wrote:
> On Fri, May 31, 2024 at 09:31:24AM -0700, Kees Cook 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.
> >
> > This is great! Is the target v6.11 or v6.10 for these?
> >
> > -Kees
> >
> > > 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.
> @kees: Since you have probably done these before, I'll ask you the
> questions:
>
> 1. The idea is to send Linus the treewide-constify patch on its own at
> the end of the merge window for 6.11. Right?
Right. The best time is likely around Wed on the second week of the merge
window, assuming all dependencies have landed. And it could be sent
earlier if all the dependencies land sooner than that.
> 2. Is there a special way to send these treewide patches? Or is it just
> a regular PR with an explanation on why it is being done?
I would do a regular PR with all the details for Linus to do the change
himself, but many times people send these as an explicit patch. For
example, include the full Coccinelle script, or the "sed" command
line, etc, and then detail any "by hand" changes that were needed on
top of that.
> 3. Can you please send (if there are any) me any examples where this has
> been done in the past. Maybe some lore.kernel.org links?
I found this one that is a good example, though it's a PATCH not a GIT PULL:
https://lore.kernel.org/lkml/20221220134519.3dd1318b@gandalf.local.home/
became
https://git.kernel.org/linus/292a089d78d3e2f7944e60bb897c977785a321e3
-Kees
--
Kees Cook
next prev parent reply other threads:[~2024-06-06 18:52 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 [this message]
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
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=202406061143.27C12F44A3@keescook \
--to=kees@kernel.org \
--cc=j.granados@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=thomas@t-8ch.de \
/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®