[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230120152250.GA9801@redhat.com>
Date: Fri, 20 Jan 2023 16:22:51 +0100
From: Oleg Nesterov <oleg@...hat.com>
To: Gregory Price <gourry.memverge@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kselftest@...r.kernel.org,
krisman@...labora.com, tglx@...utronix.de, luto@...nel.org,
peterz@...radead.org, ebiederm@...ssion.com,
akpm@...ux-foundation.org, adobriyan@...il.com, corbet@....net,
shuah@...nel.org, Gregory Price <gregory.price@...verge.com>
Subject: Re: [PATCH v3 1/3] ptrace,syscall_user_dispatch: Implement Syscall
User Dispatch Suspension
Hi Gregory,
I'll try to read this series next Monday, I need to recall what does
syscall-user-dispatch actually do ;)
just one question for now,
On 01/20, Gregory Price wrote:
>
> --- a/kernel/ptrace.c
> +++ b/kernel/ptrace.c
> @@ -370,6 +370,10 @@ static int check_ptrace_options(unsigned long data)
> if (data & ~(unsigned long)PTRACE_O_MASK)
> return -EINVAL;
>
> + if (unlikely(data & PTRACE_O_SUSPEND_SYSCALL_USER_DISPATCH) &&
> + (!IS_ENABLED(CONFIG_CHECKPOINT_RESTART)))
> + return -EINVAL;
Hmm? git grep CHECKPOINT_RESTART shows nothing.
Oleg.
Powered by blists - more mailing lists