From: Gregory Price <gourry@gourry.net>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Matthew Wilcox <willy@infradead.org>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
corbet@lwn.net, skhan@linuxfoundation.org, tglx@kernel.org,
peterz@infradead.org, luto@kernel.org, akpm@linux-foundation.org,
feng.tang@linux.alibaba.com, pmladek@suse.com,
lance.yang@linux.dev, marc.herbert@linux.intel.com,
kees@kernel.org, leitao@debian.org, joel.granados@kernel.org,
lirongqing@baidu.com, nathan@kernel.org, xur@google.com,
lukas.bulwahn@redhat.com, ryan.roberts@arm.com
Subject: Re: [PATCH v2 1/2] syscall_user_dispatch: Make it configurable in Kconfig
Date: Sun, 5 Jul 2026 20:11:14 -0400 [thread overview]
Message-ID: <akryoj42VnTnHrbW@fedora> (raw)
In-Reply-To: <50697183-B97D-48A9-B0C4-A288B88324DC@infradead.org>
On Sun, Jul 05, 2026 at 02:49:56PM -0700, Randy Dunlap wrote:
> On July 4, 2026 8:22:20 AM PDT, Matthew Wilcox <willy@infradead.org> wrote:
> >On Fri, Jul 03, 2026 at 09:58:58PM -0400, Gregory Price wrote:
> >> +config SYSCALL_USER_DISPATCH
> >> + bool "Syscall User Dispatch"
> >> + depends on GENERIC_ENTRY
> >> + default y
> >> + help
> >> + Syscall User Dispatch lets a thread have its own system calls outside
> >> + an allowed IP address range to be intercepted and redirected to a
> >> + userspace signal handler.
> >
> >I was very confused when I read this. IP expands to Internet Protocol
> >long before it gets to Instruction Pointer in my brain.
> >
>
> Ditto
>
ack.
next prev parent reply other threads:[~2026-07-06 0:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 1:58 [PATCH v2 0/2] syscall_user_dispatch: add build/runtime configs Gregory Price
2026-07-04 1:58 ` [PATCH v2 1/2] syscall_user_dispatch: Make it configurable in Kconfig Gregory Price
2026-07-04 15:22 ` Matthew Wilcox
2026-07-04 15:29 ` Gregory Price
2026-07-05 21:49 ` Randy Dunlap
2026-07-06 0:11 ` Gregory Price [this message]
2026-07-05 20:31 ` Thomas Gleixner
2026-07-06 0:10 ` Gregory Price
2026-07-04 1:58 ` [PATCH v2 2/2] syscall_user_dispatch: add kernel.syscall_user_dispatch sysctl Gregory Price
2026-07-05 20:35 ` Thomas Gleixner
2026-07-06 0:07 ` Gregory Price
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=akryoj42VnTnHrbW@fedora \
--to=gourry@gourry.net \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=feng.tang@linux.alibaba.com \
--cc=joel.granados@kernel.org \
--cc=kees@kernel.org \
--cc=lance.yang@linux.dev \
--cc=leitao@debian.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=nathan@kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rdunlap@infradead.org \
--cc=ryan.roberts@arm.com \
--cc=skhan@linuxfoundation.org \
--cc=tglx@kernel.org \
--cc=willy@infradead.org \
--cc=xur@google.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