From: Gregory Price <gourry.memverge@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-doc@vger.kernel.org, oleg@redhat.com, avagin@gmail.com,
peterz@infradead.org, luto@kernel.org, krisman@collabora.com,
tglx@linutronix.de, corbet@lwn.net, shuah@kernel.org,
Gregory Price <gregory.price@memverge.com>
Subject: [PATCH v6 0/2]
Date: Tue, 24 Jan 2023 21:51:24 -0500 [thread overview]
Message-ID: <20230125025126.787431-1-gregory.price@memverge.com> (raw)
v6: drop fs/proc/array update, it's not needed
drop on_dispatch field exposure in config structure, it's not
checkpoint relevant.
(Thank you for the reviews Oleg and Andrei)
v5: automated test for !defined(GENERIC_ENTRY) failed, fix fs/proc
use ifdef for GENERIC_ENTRY || TIF_SYSCALL_USER_DISPATCH
note: syscall user dispatch is not presently supported for
non-generic entry, but could be implemented. question is
whether the TIF_ define should be carved out now or then
v4: Whitespace
s/CHECKPOINT_RESTART/CHECKPOINT_RESUME
check test_syscall_work(SYSCALL_USER_DISPATCH) to determine if it's
turned on or not in fs/proc/array and getter interface
v3: Kernel test robot static function fix
Whitespace nitpicks
v2: Implements the getter/setter interface in ptrace rather than prctl
Syscall user dispatch makes it possible to cleanly intercept system
calls from user-land. However, most transparent checkpoint software
presently leverages some combination of ptrace and system call
injection to place software in a ready-to-checkpoint state.
If Syscall User Dispatch is enabled at the time of being quiesced,
injected system calls will subsequently be interposed upon and
dispatched to the task's signal handler.
This patch set implements 2 features to enable software such as CRIU
to cleanly interpose upon software leveraging syscall user dispatch.
- Implement PTRACE_O_SUSPEND_SYSCALL_USER_DISPATCH, akin to a similar
feature for SECCOMP. This allows a ptracer to temporarily disable
syscall user dispatch, making syscall injection possible.
- Implement a getter interface for Syscall User Dispatch config info.
To resume successfully, the checkpoint/resume software has to
save and restore this information. Presently this configuration
is write-only, with no way for C/R software to save it.
This was done in ptrace because syscall user dispatch is not part of
uapi. The syscall_user_dispatch_config structure was added to the
ptrace exports.
Gregory Price (2):
ptrace,syscall_user_dispatch: Implement Syscall User Dispatch
Suspension
ptrace,syscall_user_dispatch: add a getter/setter for sud
configuration
.../admin-guide/syscall-user-dispatch.rst | 5 ++-
include/linux/ptrace.h | 2 +
include/linux/syscall_user_dispatch.h | 19 ++++++++
include/uapi/linux/ptrace.h | 15 ++++++-
kernel/entry/syscall_user_dispatch.c | 45 +++++++++++++++++++
kernel/ptrace.c | 13 ++++++
6 files changed, 97 insertions(+), 2 deletions(-)
--
2.39.0
next reply other threads:[~2023-01-25 2:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 2:51 Gregory Price [this message]
2023-01-25 2:51 ` [PATCH v6 1/2] ptrace,syscall_user_dispatch: Implement Syscall User Dispatch Suspension Gregory Price
2023-01-26 0:30 ` Oleg Nesterov
2023-01-26 1:30 ` Gregory Price
2023-01-26 4:43 ` Gregory Price
[not found] ` <CANaxB-xn0wW5xA_CT7bA5=jig+td__EDKPBWSpZdfgMgVOezCg@mail.gmail.com>
2023-01-26 5:26 ` Gregory Price
2023-01-26 15:10 ` Oleg Nesterov
2023-01-26 18:09 ` Andrei Vagin
2023-01-26 15:07 ` Oleg Nesterov
2023-01-26 17:45 ` Andrei Vagin
2023-01-26 17:52 ` Gregory Price
2023-01-26 18:30 ` Andrei Vagin
2023-01-26 18:30 ` Oleg Nesterov
2023-01-26 18:46 ` Gregory Price
2023-01-26 18:53 ` Andrei Vagin
2023-01-26 19:01 ` Gregory Price
2023-01-25 2:51 ` [PATCH v6 2/2] ptrace,syscall_user_dispatch: add a getter/setter for sud configuration Gregory Price
2023-01-25 7:14 ` kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2023-05-15 0:40 [PATCH v6 0/2] alison
2018-11-05 18:21 Mark Salyzyn
2018-11-05 18:55 ` Amir Goldstein
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=20230125025126.787431-1-gregory.price@memverge.com \
--to=gourry.memverge@gmail.com \
--cc=avagin@gmail.com \
--cc=corbet@lwn.net \
--cc=gregory.price@memverge.com \
--cc=krisman@collabora.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).