From: Bradley Morgan <include@grrlz.net>
To: rdunlap@infradead.org
Cc: broonie@kernel.org, corbet@lwn.net, gourry@gourry.net,
joel.granados@kernel.org, kees@kernel.org,
kmehltretter@gmail.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
luto@kernel.org, oleg@redhat.com, peterz@infradead.org,
sfr@canb.auug.org.au, skhan@linuxfoundation.org, tglx@kernel.org
Subject: Re: [PATCH v2] syscall_user_dispatch: Use CONFIG_SYSCTL for sysctl guard
Date: Sat, 22 Aug 2026 18:37:24 +0100 [thread overview]
Message-ID: <CDF0DEFD-3136-48AD-BEE6-B01C709E5739@grrlz.net> (raw)
In-Reply-To: <1842ee57-ff3b-42df-b6c7-c93d395a3944@infradead.org>
On 22 August 2026 18:35:14 BST, Randy Dunlap <rdunlap@infradead.org> wrote:
>
>
>On 8/22/26 12:23 AM, Karl Mehltretter wrote:
>> Commit 8d75c338f0bc ("sysctl: remove CONFIG_PROC_SYSCTL, it just mirrors
>> CONFIG_SYSCTL") removed CONFIG_PROC_SYSCTL, but the sysctl added by
>> commit 5b6e32ba7b59 ("syscall_user_dispatch: Add
>> kernel.syscall_user_dispatch sysctl") is still guarded by it. Now that
>> both commits are merged, kernel.syscall_user_dispatch is no longer
>> registered.
>>
>> syscall_user_dispatch_allowed defaults to true. SUD therefore remains
>> available, but administrators cannot disable new activations.
>>
>> Use CONFIG_SYSCTL for the guard and documentation.
>>
>> Fixes: 5b6e32ba7b59 ("syscall_user_dispatch: Add
>kernel.syscall_user_dispatch sysctl")
>> Assisted-by: Codex:gpt-5.6-sol
>> Acked-by: Oleg Nesterov <oleg@redhat.com>
>> Reviewed-by: Joel Granados <joel.granados@kernel.org>
Reviewed-by: Bradley Morgan <include@grrlz.net>
>> Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
>
>Acked-by: Randy Dunlap <rdunlap@infradead.org>
>Thanks.
>
>> ---
>> Changes in v2:
>> - Reword changelog and rebase onto mainline now that both commits
>> are merged there (v7.2 is unaffected, it has neither commit).
>> - Collected Acked-by/Reviewed-by tags from v1. No code change.
>>
>> v1:
>https://lore.kernel.org/all/20260813062039.14567-1-kmehltretter@gmail.com/
>>
>> Documentation/admin-guide/sysctl/kernel.rst | 2 +-
>> kernel/entry/syscall_user_dispatch.c | 4 ++--
>> 2 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/Documentation/admin-guide/sysctl/kernel.rst
>b/Documentation/admin-guide/sysctl/kernel.rst
>> index b6328cd0f43e..ffea61d448eb 100644
>> --- a/Documentation/admin-guide/sysctl/kernel.rst
>> +++ b/Documentation/admin-guide/sysctl/kernel.rst
>> @@ -1416,7 +1416,7 @@ Controls whether userspace may arm Syscall User
>Dispatch via
>> ==
>===================================================================
>>
>> Only present when the kernel is built with
>``CONFIG_SYSCALL_USER_DISPATCH``
>> -and ``CONFIG_PROC_SYSCTL``.
>> +and ``CONFIG_SYSCTL``.
Ack.
>>
>>
>> sysctl_writes_strict
>> diff --git a/kernel/entry/syscall_user_dispatch.c
>b/kernel/entry/syscall_user_dispatch.c
>> index 2002c7aae435..59c861866941 100644
>> --- a/kernel/entry/syscall_user_dispatch.c
>> +++ b/kernel/entry/syscall_user_dispatch.c
>> @@ -178,7 +178,7 @@ int syscall_user_dispatch_set_config(struct
>task_struct *task, unsigned long siz
>> (char __user *)(uintptr_t)cfg.selector);
>> }
>>
>> -#ifdef CONFIG_PROC_SYSCTL
>> +#ifdef CONFIG_SYSCTL
Ack.
>> static const struct ctl_table syscall_user_dispatch_sysctls[] = {
>> {
>> .procname = "syscall_user_dispatch",
>> @@ -195,4 +195,4 @@ static int __init
>syscall_user_dispatch_sysctl_init(void)
>> return 0;
>> }
>> late_initcall(syscall_user_dispatch_sysctl_init);
>> -#endif /* CONFIG_PROC_SYSCTL */
>> +#endif /* CONFIG_SYSCTL */
>>
>> base-commit: 26260251022fbc2f248a3d747a9b2b961b18d2d8
>
>
Thanks!
prev parent reply other threads:[~2026-08-22 17:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 6:20 [PATCH] syscall_user_dispatch: Use CONFIG_SYSCTL for sysctl guard Karl Mehltretter
2026-08-13 15:09 ` Oleg Nesterov
2026-08-14 10:55 ` Joel Granados
2026-08-22 7:23 ` [PATCH v2] " Karl Mehltretter
2026-08-22 17:35 ` Randy Dunlap
2026-08-22 17:37 ` Bradley Morgan [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=CDF0DEFD-3136-48AD-BEE6-B01C709E5739@grrlz.net \
--to=include@grrlz.net \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=gourry@gourry.net \
--cc=joel.granados@kernel.org \
--cc=kees@kernel.org \
--cc=kmehltretter@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=luto@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=skhan@linuxfoundation.org \
--cc=tglx@kernel.org \
/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