From: Oleg Nesterov <oleg@redhat.com>
To: Joel Granados <joel.granados@kernel.org>
Cc: Mark Brown <broonie@kernel.org>,
Luis Chamberlain <mcgrof@kernel.org>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Kees Cook <kees@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH sysctl-next 1/2] sysctl: collapse redundant CONFIG_SYSCTL nesting in kernel/sysctl.c
Date: Mon, 10 Aug 2026 14:24:53 +0200 [thread overview]
Message-ID: <annDFSaXge3or8kd@redhat.com> (raw)
In-Reply-To: <6vgzwppmbvwbkiwzty3ki6ayqt6li7gr7nlurlp5ip6jyt7osu@wedlfafsqr6i>
On 08/10, Joel Granados wrote:
>
> This looks very nice, but now that you are there, I would propose an
> additional change:
>
> 1. I would move the proc_do_static_key function and the definition of
> the sysctl_subsys_table into the first CONFIG_SYSCTL definition
> section; right after proc_do_large_bitmap
>
> 2. Doing one means that there is only one #ifdef CONFIG_SYSCTL
>
> 3. Add a proc_do_static_key stub to the #else section; something like
> this:
>
> int proc_do_static_key(const struct ctl_table *table, int dir,
> void *buffer, size_t *lenp, loff_t *ppos)
> {
> return -ENOSYS;
> }
Yeees, and I thought about this too ;) Just I decided to send the
minimal and trivial cleanup. Except right now I am not 100% sure
about 3. because I can't read the source code now...
Again, I'd be happy to send V2, but only after I return from PTO on
Aug 19.
But let me ask... Do you want me to incorporate this additional change
into 1/2 or send it as a separate change? I'd prefer the latter, but
I am fine either way.
Oleg.
prev parent reply other threads:[~2026-08-10 12:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 15:47 [PATCH sysctl-next 1/2] sysctl: collapse redundant CONFIG_SYSCTL nesting in kernel/sysctl.c Oleg Nesterov
2026-08-07 15:48 ` [PATCH sysctl-next 2/2] sysctl: remove redundant CONFIG_PROC_FS checks Oleg Nesterov
2026-08-07 18:01 ` Bradley Morgan
2026-08-10 10:58 ` Joel Granados
2026-08-10 12:07 ` Oleg Nesterov
2026-08-07 17:16 ` [PATCH sysctl-next 1/2] sysctl: collapse redundant CONFIG_SYSCTL nesting in kernel/sysctl.c Bradley Morgan
2026-08-10 11:08 ` Joel Granados
2026-08-10 12:24 ` Oleg Nesterov [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=annDFSaXge3or8kd@redhat.com \
--to=oleg@redhat.com \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=jack@suse.cz \
--cc=joel.granados@kernel.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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