From: Thomas Gleixner <tglx@kernel.org>
To: Gregory Price <gourry@gourry.net>, linux-kernel@vger.kernel.org
Cc: linux-doc@vger.kernel.org, kernel-team@meta.com, corbet@lwn.net,
skhan@linuxfoundation.org, peterz@infradead.org, luto@kernel.org,
akpm@linux-foundation.org, feng.tang@linux.alibaba.com,
pmladek@suse.com, mhiramat@kernel.org,
marc.herbert@linux.intel.com, joel.granados@kernel.org,
gourry@gourry.net, lirongqing@baidu.com, kees@kernel.org,
nathan@kernel.org, linusw@kernel.org, arnd@arndb.de,
deller@gmx.de, jpoimboe@kernel.org, ruanjinjie@huawei.com,
lukas.bulwahn@redhat.com, ryan.roberts@arm.com, ojeda@kernel.org
Subject: Re: [PATCH 2/2] kernel/entry: add kernel.syscall_user_dispatch sysctl
Date: Fri, 03 Jul 2026 17:46:40 +0200 [thread overview]
Message-ID: <877bncm5y7.ffs@fw13> (raw)
In-Reply-To: <20260627205551.769684-2-gourry@gourry.net>
On Sat, Jun 27 2026 at 16:55, Gregory Price wrote:
Same comment vs. subject prefix.
> Add a matching sysctl to go with CONFIG_SYSCALL_USER_DISPATCH.
>
> kernel.syscall_user_dispatch (default 1) controls whether userspace
> may arm SUD (both via prctl and ptrace).
What's SUD again? This is a changelog and not twatter.
> + /* Arming can be denied at runtime via sysctl, disarming is allowed */
> + if (mode != PR_SYS_DISPATCH_OFF && !syscall_user_dispatch_allowed)
> + return -EPERM;
That might be similar to other sysctls, but if an application had it
enabled prior to the sysctl=off toggle, then that application will
suddenly fail in operation if it requires to move the dispatch window.
Thanks,
tglx
next prev parent reply other threads:[~2026-07-03 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-27 20:55 [PATCH 1/2] kernel/entry: add CONFIG_SYSCALL_USER_DISPATCH to compile SUD out Gregory Price
2026-06-27 20:55 ` [PATCH 2/2] kernel/entry: add kernel.syscall_user_dispatch sysctl Gregory Price
2026-07-03 15:46 ` Thomas Gleixner [this message]
2026-07-03 17:26 ` Gregory Price
2026-07-03 19:06 ` Thomas Gleixner
2026-07-03 15:39 ` [PATCH 1/2] kernel/entry: add CONFIG_SYSCALL_USER_DISPATCH to compile SUD out Thomas Gleixner
2026-07-03 17:22 ` Gregory Price
2026-07-03 19:05 ` Thomas Gleixner
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=877bncm5y7.ffs@fw13 \
--to=tglx@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=deller@gmx.de \
--cc=feng.tang@linux.alibaba.com \
--cc=gourry@gourry.net \
--cc=joel.granados@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=kees@kernel.org \
--cc=kernel-team@meta.com \
--cc=linusw@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=lukas.bulwahn@redhat.com \
--cc=luto@kernel.org \
--cc=marc.herbert@linux.intel.com \
--cc=mhiramat@kernel.org \
--cc=nathan@kernel.org \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=ruanjinjie@huawei.com \
--cc=ryan.roberts@arm.com \
--cc=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.