From: Rodrigo Campos <rodrigo@kinvolk.io>
To: Sargun Dhillon <sargun@sargun.me>
Cc: Giuseppe Scrivano <gscrivan@redhat.com>,
Kees Cook <keescook@chromium.org>,
Linux Containers <containers@lists.linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] Handle seccomp notification preemption
Date: Tue, 23 Mar 2021 18:25:03 +0100 [thread overview]
Message-ID: <CACaBj2bxYks-6zOwfzDq_0B0UqgxTY74psp4PCz78jbxqhKVJQ@mail.gmail.com> (raw)
In-Reply-To: <20210318051726.2488-1-sargun@sargun.me>
On Thu, Mar 18, 2021 at 6:17 AM Sargun Dhillon <sargun@sargun.me> wrote:
> Changes since v1[1]:
> * Fix some documentation
> * Add Rata's patches to allow for direct return from addfd
>
> [1]: https://lore.kernel.org/lkml/20210220090502.7202-1-sargun@sargun.me/
> [2]: https://lore.kernel.org/lkml/202012011322.26DCBC64F2@keescook/
>
> Rodrigo Campos (1):
> seccomp: Support atomic "addfd + send reply"
>
> Sargun Dhillon (4):
> seccomp: Refactor notification handler to prepare for new semantics
> seccomp: Add wait_killable semantic to seccomp user notifier
> selftests/seccomp: Add test for wait killable notifier
> selftests/seccomp: Add test for atomic addfd+send
Friendly ping. Any review comments on these patches? :)
_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/containers
next prev parent reply other threads:[~2021-03-23 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 5:17 [PATCH 0/5] Handle seccomp notification preemption Sargun Dhillon
2021-03-23 17:25 ` Rodrigo Campos [this message]
2021-03-18 5:17 Sargun Dhillon
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=CACaBj2bxYks-6zOwfzDq_0B0UqgxTY74psp4PCz78jbxqhKVJQ@mail.gmail.com \
--to=rodrigo@kinvolk.io \
--cc=containers@lists.linux-foundation.org \
--cc=gscrivan@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sargun@sargun.me \
/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).