[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230123154101.GA6268@redhat.com>
Date: Mon, 23 Jan 2023 16:41:02 +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 3/3] ptrace,syscall_user_dispatch: add a getter/setter
for sud configuration
On 01/22, Gregory Price wrote:
>
> +int syscall_user_dispatch_get_config(struct task_struct *task, unsigned long size,
> + void __user *data)
> +{
> + struct syscall_user_dispatch *sd = &task->syscall_dispatch;
> + struct syscall_user_dispatch_config config;
> +
> + if (size != sizeof(struct syscall_user_dispatch_config))
> + return -EINVAL;
> +
> + if (test_syscall_work(SYSCALL_USER_DISPATCH))
> + config.mode = PR_SYS_DISPATCH_ON;
> + else
> + config.mode = PR_SYS_DISPATCH_OFF;
Stupid question...
Why do we need 2/3 (which reports SYSCALL_USER_DISPATCH in proc/pid/status) then?
Oleg.
Powered by blists - more mailing lists