From: Alexey Gladkov <legion@kernel.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nsc@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/1] sysctl: remove CONFIG_SYSCTL, it just mirrors CONFIG_PROC_SYSCTL
Date: Wed, 22 Jul 2026 15:07:56 +0200 [thread overview]
Message-ID: <amDArBvxjBRsmCvs@example.org> (raw)
In-Reply-To: <amC7F7oKFjYKcQW2@redhat.com>
On Wed, Jul 22, 2026 at 02:44:07PM +0200, Oleg Nesterov wrote:
> Andrew, Eric, et al,
>
> To me it is a bit annoying/confusing to see both CONFIG_PROC_SYSCTL and
> CONFIG_SYSCTL in the source code (they are the same thing), but...
>
> Does it make any sense to try to suggest this patch for -mm tree?
>
> It is hopefully trivial (generated by 2 perl one-liners) but touches 170 files.
> So far I don't even CC maintainers, the output of get_maintainer.pl is huge.
>
> Alternatively, we could kill CONFIG_PROC_SYSCTL in favour of CONFIG_SYSCTL.
> This would result in a much smaller patch, but I am not sure if it is "safe"
> because CONFIG_PROC_SYSCTL is user-visible in that it has a prompt in
> fs/proc/Kconfig. But perhaps this is fine?
>
> (either way we can make a couple more minor cleanups if we kill one of them).
After 61a47c1ad3a4 ("sysctl: Remove the sysctl system call"), we have no
other way to set sysctl values except through /proc/sys.
So it makes sense for me to remove the duplicates.
--
Rgrds, legion
prev parent reply other threads:[~2026-07-22 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 12:44 [RFC PATCH 0/1] sysctl: remove CONFIG_SYSCTL, it just mirrors CONFIG_PROC_SYSCTL Oleg Nesterov
2026-07-22 12:44 ` [RFC PATCH 1/1] " Oleg Nesterov
2026-07-22 13:07 ` Alexey Gladkov [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=amDArBvxjBRsmCvs@example.org \
--to=legion@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=oleg@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