From: Kees Cook <keescook@chromium.org>
To: Andrei Vagin <avagin@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Christian Brauner <brauner@kernel.org>,
linux-kernel@vger.kernel.org, Andrei Vagin <avagin@gmail.com>,
Andy Lutomirski <luto@amacapital.net>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Peter Oskolkov <posk@google.com>,
Tycho Andersen <tycho@tycho.pizza>,
Will Drewry <wad@chromium.org>,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: [PATCH 0/5 v3] seccomp: add the synchronous mode for seccomp_unotify
Date: Fri, 18 Nov 2022 14:38:21 -0800 [thread overview]
Message-ID: <202211181438.7D252CDC10@keescook> (raw)
In-Reply-To: <20221111073154.784261-1-avagin@google.com>
On Thu, Nov 10, 2022 at 11:31:49PM -0800, Andrei Vagin wrote:
> From: Andrei Vagin <avagin@gmail.com>
>
> seccomp_unotify allows more privileged processes do actions on behalf
> of less privileged processes.
>
> In many cases, the workflow is fully synchronous. It means a target
> process triggers a system call and passes controls to a supervisor
> process that handles the system call and returns controls back to the
> target process. In this context, "synchronous" means that only one
> process is running and another one is waiting.
>
> The new WF_CURRENT_CPU flag advises the scheduler to move the wakee to
> the current CPU. For such synchronous workflows, it makes context
> switches a few times faster.
>
> Right now, each interaction takes 12µs. With this patch, it takes about
> 3µs.
>
> v2: clean up the first patch and add the test.
> v3: update commit messages and a few fixes suggested by Kees Cook.
Thanks for the update! If I can get Acks from the sched folks, I think
this looks good to take.
-Kees
>
> Cc: Andy Lutomirski <luto@amacapital.net>
> Cc: Christian Brauner <brauner@kernel.org>
> Cc: Dietmar Eggemann <dietmar.eggemann@arm.com>
> Cc: Kees Cook <keescook@chromium.org>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Juri Lelli <juri.lelli@redhat.com>
> Cc: Peter Oskolkov <posk@google.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Tycho Andersen <tycho@tycho.pizza>
> Cc: Will Drewry <wad@chromium.org>
> Cc: Vincent Guittot <vincent.guittot@linaro.org>
>
> Andrei Vagin (4):
> seccomp: don't use semaphore and wait_queue together
> sched: add a few helpers to wake up tasks on the current cpu
> seccomp: add the synchronous mode for seccomp_unotify
> selftest/seccomp: add a new test for the sync mode of
> seccomp_user_notify
>
> Peter Oskolkov (1):
> sched: add WF_CURRENT_CPU and externise ttwu
>
> include/linux/completion.h | 1 +
> include/linux/swait.h | 1 +
> include/linux/wait.h | 3 +
> include/uapi/linux/seccomp.h | 4 +
> kernel/sched/completion.c | 12 +++
> kernel/sched/core.c | 5 +-
> kernel/sched/fair.c | 4 +
> kernel/sched/sched.h | 13 +--
> kernel/sched/swait.c | 11 +++
> kernel/sched/wait.c | 5 ++
> kernel/seccomp.c | 72 +++++++++++++--
> tools/testing/selftests/seccomp/seccomp_bpf.c | 88 +++++++++++++++++++
> 12 files changed, 204 insertions(+), 15 deletions(-)
>
> --
> 2.37.2
>
--
Kees Cook
next prev parent reply other threads:[~2022-11-18 22:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 7:31 [PATCH 0/5 v3] seccomp: add the synchronous mode for seccomp_unotify Andrei Vagin
2022-11-11 7:31 ` [PATCH 1/5] seccomp: don't use semaphore and wait_queue together Andrei Vagin
2022-11-11 7:31 ` [PATCH 2/5] sched: add WF_CURRENT_CPU and externise ttwu Andrei Vagin
2022-11-11 7:31 ` [PATCH 3/5] sched: add a few helpers to wake up tasks on the current cpu Andrei Vagin
2022-11-11 7:31 ` [PATCH 4/5] seccomp: add the synchronous mode for seccomp_unotify Andrei Vagin
2022-11-11 7:31 ` [PATCH 5/5] selftest/seccomp: add a new test for the sync mode of seccomp_user_notify Andrei Vagin
2022-11-18 22:38 ` Kees Cook [this message]
2022-11-22 7:52 ` [PATCH 0/5 v3] seccomp: add the synchronous mode for seccomp_unotify Andrei Vagin
2022-12-06 6:52 ` Andrei Vagin
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=202211181438.7D252CDC10@keescook \
--to=keescook@chromium.org \
--cc=avagin@gmail.com \
--cc=avagin@google.com \
--cc=brauner@kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=posk@google.com \
--cc=tycho@tycho.pizza \
--cc=vincent.guittot@linaro.org \
--cc=wad@chromium.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