From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Joel Granados <j.granados@samsung.com>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
Kees Cook <keescook@chromium.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH v3 0/2] sysctl: treewide: prepare ctl_table_root for ctl_table constification
Date: Fri, 22 Mar 2024 17:31:37 +0100 [thread overview]
Message-ID: <e4de72dc-8dad-4c57-85b3-174272bd1530@t-8ch.de> (raw)
In-Reply-To: <20240322124709.w5ntjwb5tbumltoy@joelS2.panther.com>
On 2024-03-22 13:47:09+0100, Joel Granados wrote:
> On Fri, Mar 15, 2024 at 07:11:29PM +0100, Thomas Weißschuh wrote:
> > The two patches were previously submitted on their own.
> > In commit f9436a5d0497
> > ("sysctl: allow to change limits for posix messages queues")
> > a code dependency was introduced between the two callbacks.
> > This code dependency results in a dependency between the two patches, so
> > now they are submitted as a series.
> >
> > The series is meant to be merged via the sysctl tree.
> >
> > There is an upcoming series that will introduce a new implementation of
> > .set_ownership and .permissions which would need to be adapted [0].
> >
> > These changes ere originally part of the sysctl-const series [1].
> > To slim down that series and reduce the message load on other
> > maintainers to a minimum, the patches are split out.
> >
> > [0] https://lore.kernel.org/lkml/20240222160915.315255-1-aleksandr.mikhalitsyn@canonical.com/
> > [1] https://lore.kernel.org/lkml/20231204-const-sysctl-v2-2-7a5060b11447@weissschuh.net/
> >
> > Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> > ---
> > Changes in v3:
> > - Drop now spurious argument in fs/proc/proc_sysctl.c
> > - Rebase on next-20240315
> > - Incorporate permissions patch.
> > - Link to v2 (ownership): https://lore.kernel.org/r/20240223-sysctl-const-ownership-v2-1-f9ba1795aaf2@weissschuh.net
> > - Link to v1 (permissions): https://lore.kernel.org/r/20231226-sysctl-const-permissions-v1-1-5cd3c91f6299@weissschuh.net
> >
> > Changes in v2:
> > - Rework commit message
> > - Mention potential conflict with upcoming per-namespace kernel.pid_max
> > sysctl
> > - Delete unused parameter table
> > - Link to v1: https://lore.kernel.org/r/20231226-sysctl-const-ownership-v1-1-d78fdd744ba1@weissschuh.net
> >
> > ---
> > Thomas Weißschuh (2):
> > sysctl: treewide: drop unused argument ctl_table_root::set_ownership(table)
> > sysctl: treewide: constify argument ctl_table_root::permissions(table)
> >
> > fs/proc/proc_sysctl.c | 2 +-
> > include/linux/sysctl.h | 3 +--
> > ipc/ipc_sysctl.c | 5 ++---
> > ipc/mq_sysctl.c | 5 ++---
> > kernel/ucount.c | 2 +-
> > net/sysctl_net.c | 3 +--
> > 6 files changed, 8 insertions(+), 12 deletions(-)
> > ---
> > base-commit: a1e7655b77e3391b58ac28256789ea45b1685abb
> > change-id: 20231226-sysctl-const-ownership-ff75e67b4eea
> >
> > Best regards,
> > --
> > Thomas Weißschuh <linux@weissschuh.net>
> >
>
> Will put this to test and then try to rebase it to 6.9-rc1 once it comes
> out.
Thanks!
Your changes to the commit messages look good.
For my other changes I'm planning to resubmit all of them during the
weekend or next week.
Thomas
prev parent reply other threads:[~2024-03-22 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240315181141eucas1p267385cd08f77d720e58b038be06d292e@eucas1p2.samsung.com>
2024-03-15 18:11 ` Thomas Weißschuh
2024-03-15 18:11 ` [PATCH v3 1/2] sysctl: treewide: drop unused argument ctl_table_root::set_ownership(table) Thomas Weißschuh
2024-03-22 12:45 ` Joel Granados
2024-03-15 18:11 ` [PATCH v3 2/2] sysctl: treewide: constify argument ctl_table_root::permissions(table) Thomas Weißschuh
2024-03-22 12:32 ` Joel Granados
2024-03-22 12:47 ` [PATCH v3 0/2] sysctl: treewide: prepare ctl_table_root for ctl_table constification Joel Granados
2024-03-22 16:31 ` Thomas Weißschuh [this message]
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=e4de72dc-8dad-4c57-85b3-174272bd1530@t-8ch.de \
--to=linux@weissschuh.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=j.granados@samsung.com \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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®