From: Mauricio Faria de Oliveira <mfo@igalia.com>
To: sashiko-reviews@lists.linux.dev
Cc: Christian Borntraeger <borntraeger@linux.ibm.com>,
linux-s390@vger.kernel.org, Heiko Carstens <hca@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
mptcp@lists.linux.dev, Vasily Gorbik <gor@linux.ibm.com>,
bpf@vger.kernel.org
Subject: Re: [PATCH RFC v2 02/13] proc: add config option SYSCTL_MODULE_ALIASES
Date: Wed, 19 Aug 2026 13:24:55 -0300 [thread overview]
Message-ID: <253d5572bd8c3020775b61e8ac9eb675@igalia.com> (raw)
In-Reply-To: <20260819023701.5197B1F000E9@smtp.kernel.org>
On 2026-08-18 23:37, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
> - [Low] The Kconfig option `SYSCTL_MODULE_ALIASES` is introduced but never used in the codebase.
It's used in later patches; apparently not a problem.
> - [Low] Grammatical error in the Kconfig help text: 'This options adds' should be 'This option adds'.
Fixed.
> --
>
> --- Patch [2]: [PATCH RFC v2 02/13] proc: add config option SYSCTL_MODULE_ALIASES ---
> commit 931fa1a5261f1467829ad7b64b387a4e318eb177
> Author: Mauricio Faria de Oliveira <mfo@igalia.com>
>
> proc: add config option SYSCTL_MODULE_ALIASES
>
> Add a config option for the 'sysctl:' module aliases feature.
>
>> diff --git a/fs/proc/Kconfig b/fs/proc/Kconfig
>> index 24f5a36f45df8..e6591ec4bcf0a 100644
>> --- a/fs/proc/Kconfig
>> +++ b/fs/proc/Kconfig
>> @@ -98,6 +98,19 @@ config SYSCTL
>> building a kernel for install/rescue disks or your system is very
>> limited in memory.
>>
>> +config SYSCTL_MODULE_ALIASES
>> + bool "'sysctl:' module aliases (EXPERIMENTAL)"
>
> [Severity: Low]
> Is this config option fully implemented in this commit? The
> SYSCTL_MODULE_ALIASES option is being introduced here, but it doesn't look
> like CONFIG_SYSCTL_MODULE_ALIASES is referenced anywhere else in the C code,
> Makefiles, or scripts.
>
>> + depends on SYSCTL && MODULES
>> + default n
>> + help
>> + The /proc/sys files registered by a module do not exist until the
>> + module is loaded; meanwhile, userspace cannot find or access them.
>> +
>> + This options adds 'sysctl:*/<path>/<file>' module aliases for the
>
> [Severity: Low]
> This isn't a bug, but there is a typo in the help text: "This options adds"
> should likely be "This option adds".
>
>> + /proc/sys files registered by modules, so modules for nonexistent
>> + files can be loaded with 'modprobe sysctl:/proc/sys/<path>/<file>'
>> + by userspace when needed.
--
Mauricio
next prev parent reply other threads:[~2026-08-19 16:24 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 2:27 [PATCH RFC v2 00/13] sysctl: add module aliases Mauricio Faria de Oliveira
2026-08-19 2:28 ` [PATCH RFC v2 01/13] keys, pidns, fs/verity, riscv/vector: reorder '#include <linux/sysctl.h>' Mauricio Faria de Oliveira
2026-08-19 2:33 ` sashiko-bot
2026-08-19 2:28 ` [PATCH RFC v2 02/13] proc: add config option SYSCTL_MODULE_ALIASES Mauricio Faria de Oliveira
2026-08-19 2:37 ` sashiko-bot
2026-08-19 16:24 ` Mauricio Faria de Oliveira [this message]
2026-08-19 2:28 ` [PATCH RFC v2 03/13] sysctl, mod_devicetable: add macro MODULE_SYSCTL_TABLE Mauricio Faria de Oliveira
2026-08-19 2:40 ` sashiko-bot
2026-08-19 16:26 ` Mauricio Faria de Oliveira
2026-08-19 2:28 ` [PATCH RFC v2 04/13] sysctl: add register_sysctl() wrapper for MODULE_SYSCTL_TABLE Mauricio Faria de Oliveira
2026-08-19 2:44 ` sashiko-bot
2026-08-19 16:25 ` Mauricio Faria de Oliveira
2026-08-19 2:28 ` [PATCH RFC v2 05/13] sysctl, parport: update register_sysctl() callers with template arguments Mauricio Faria de Oliveira
2026-08-19 2:44 ` sashiko-bot
2026-08-19 16:25 ` Mauricio Faria de Oliveira
2026-08-19 2:28 ` [PATCH RFC v2 06/13] sysctl, net: add register_net_sysctl{_sz}() wrappers for MODULE_SYSCTL_TABLE Mauricio Faria de Oliveira
2026-08-19 2:40 ` sashiko-bot
2026-08-19 16:25 ` Mauricio Faria de Oliveira
2026-08-19 2:28 ` [PATCH RFC v2 07/13] sysctl, net: update register_net_sysctl{_sz}() callers with template arguments Mauricio Faria de Oliveira
2026-08-19 2:48 ` sashiko-bot
2026-08-19 16:25 ` Mauricio Faria de Oliveira
2026-08-19 2:28 ` [PATCH RFC v2 08/13] sysctl, net: update register_net_sysctl_sz(ARRAY_SIZE(table_tmpl)) " Mauricio Faria de Oliveira
2026-08-19 2:36 ` sashiko-bot
2026-08-19 2:28 ` [PATCH RFC v2 09/13] sysctl, ipv6: update register_net_sysctl{_sz}() callers " Mauricio Faria de Oliveira
2026-08-19 2:36 ` sashiko-bot
2026-08-19 2:28 ` [PATCH RFC v2 10/13] sysctl, net: update register_net_sysctl_sz() edge case Mauricio Faria de Oliveira
2026-08-19 2:39 ` sashiko-bot
2026-08-19 2:28 ` [PATCH RFC v2 11/13] sysctl: unrandomize struct ctl_table.procname Mauricio Faria de Oliveira
2026-08-19 2:38 ` sashiko-bot
2026-08-19 2:28 ` [PATCH RFC v2 12/13] modpost: move addend_*_rel() calls into addend_rel() Mauricio Faria de Oliveira
2026-08-19 2:39 ` sashiko-bot
2026-08-19 2:28 ` [PATCH RFC v2 13/13] modpost: handle MODULE_SYSCTL_TABLE symbols Mauricio Faria de Oliveira
2026-08-19 2:48 ` sashiko-bot
2026-08-19 16:29 ` Mauricio Faria de Oliveira
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=253d5572bd8c3020775b61e8ac9eb675@igalia.com \
--to=mfo@igalia.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=bpf@vger.kernel.org \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=sashiko-reviews@lists.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