From: Oleg Nesterov <oleg@redhat.com>
To: Gregory Price <gourry.memverge@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
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: Re: [PATCH v7 1/1] ptrace,syscall_user_dispatch: checkpoint/restore support for SUD
Date: Thu, 26 Jan 2023 20:15:15 +0100 [thread overview]
Message-ID: <20230126191515.GE4069@redhat.com> (raw)
In-Reply-To: <20230126190645.18341-2-gregory.price@memverge.com>
On 01/26, Gregory Price wrote:
>
> Implement ptrace getter/setter interface for syscall user dispatch.
>
> These prctl settings are presently write-only, making it impossible to
> implement transparent checkpoint/restore via software like CRIU.
>
> 'on_dispatch' field is not exposed because it is a kernel-internal
> only field that cannot be 'true' when returning to userland.
>
> Signed-off-by: Gregory Price <gregory.price@memverge.com>
> ---
> .../admin-guide/syscall-user-dispatch.rst | 5 ++-
> include/linux/syscall_user_dispatch.h | 18 +++++++++
> include/uapi/linux/ptrace.h | 9 +++++
> kernel/entry/syscall_user_dispatch.c | 39 +++++++++++++++++++
> kernel/ptrace.c | 9 +++++
> 5 files changed, 79 insertions(+), 1 deletion(-)
Reviewed-by: Oleg Nesterov <oleg@redhat.com>
next prev parent reply other threads:[~2023-01-26 19:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 19:06 [PATCH v7 0/1] Checkpoint Support for Syscall User Dispatch Gregory Price
2023-01-26 19:06 ` [PATCH v7 1/1] ptrace,syscall_user_dispatch: checkpoint/restore support for SUD Gregory Price
2023-01-26 19:15 ` Oleg Nesterov [this message]
2023-01-28 12:03 ` kernel test robot
2023-01-28 16:11 ` kernel test robot
2023-01-28 19:49 ` kernel test robot
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=20230126191515.GE4069@redhat.com \
--to=oleg@redhat.com \
--cc=avagin@gmail.com \
--cc=corbet@lwn.net \
--cc=gourry.memverge@gmail.com \
--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=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