From: Thomas Gleixner <tglx@linutronix.de>
To: Gregory Price <gourry.memverge@gmail.com>, 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,
corbet@lwn.net, shuah@kernel.org,
Gregory Price <gregory.price@memverge.com>
Subject: Re: [PATCH v8 1/1] ptrace,syscall_user_dispatch: checkpoint/restore support for SUD
Date: Fri, 10 Feb 2023 00:45:24 +0100 [thread overview]
Message-ID: <87edqy1jzf.ffs@tglx> (raw)
In-Reply-To: <20230131144458.1980891-2-gregory.price@memverge.com>
On Tue, Jan 31 2023 at 09:44, Gregory Price wrote:
>
> +static inline int syscall_user_dispatch_get_config(struct task_struct *task, unsigned long size,
> + void __user *data)
https://www.kernel.org/doc/html/latest/process/maintainer-tip.html#line-breaks
All over the place.
> index 195ae64a8c87..6d2f3b86f932 100644
> --- a/include/uapi/linux/ptrace.h
> +++ b/include/uapi/linux/ptrace.h
> @@ -112,6 +112,15 @@ struct ptrace_rseq_configuration {
> __u32 pad;
> };
>
> +#define PTRACE_SET_SYSCALL_USER_DISPATCH_CONFIG 0x4210
> +#define PTRACE_GET_SYSCALL_USER_DISPATCH_CONFIG 0x4211
> +struct syscall_user_dispatch_config {
Can you please visibly separate the defines from the struct definition
by a newline? Glueing that stuff together is just horrible to read.
> + __u64 mode;
> + __s8 *selector;
> + __u64 offset;
> + __u64 len;
https://www.kernel.org/doc/html/latest/process/maintainer-tip.html#struct-declarations-and-initializers
Please add proper documentation to this struct. It's user space ABI and
it's not the job of the man page maintainers to figure out what this
actually means.
> +int syscall_user_dispatch_set_config(struct task_struct *task, unsigned long size,
> + void __user *data)
> +{
> + struct syscall_user_dispatch_config config;
> +
> + if (size != sizeof(struct syscall_user_dispatch_config))
> + return -EINVAL;
> +
> + if (copy_from_user(&config, data, sizeof(config)))
> + return -EFAULT;
> +
> + return set_syscall_user_dispatch(config.mode, config.offset, config.len,
> + config.selector);
How is this supposed to work? This is called from the ptracer to set the
user dispatch mode on the ptracee, i.e. on @task.
But set_syscall_user_dispatch() operates on current, which is the
ptracer itself.
Clearly well tested with the non-existant selftest, which is part of
this submission.
So please fix the above issues, add a selftest and proper documentation.
I'm neither impressed by this patch nor by the reviews.
Sigh
tglx
next prev parent reply other threads:[~2023-02-09 23:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 14:44 [PATCH v8 0/1] Checkpoint Support for Syscall User Dispatch Gregory Price
2023-01-31 14:44 ` [PATCH v8 1/1] ptrace,syscall_user_dispatch: checkpoint/restore support for SUD Gregory Price
2023-01-31 18:58 ` Oleg Nesterov
2023-02-09 20:29 ` Andrei Vagin
2023-02-09 23:45 ` Thomas Gleixner [this message]
2023-02-09 23:46 ` Thomas Gleixner
2023-02-10 1:27 ` 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=87edqy1jzf.ffs@tglx \
--to=tglx@linutronix.de \
--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=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=shuah@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;
as well as URLs for NNTP newsgroup(s).