From: Rodrigo Campos <rodrigo@kinvolk.io>
To: Sargun Dhillon <sargun@sargun.me>
Cc: "Kees Cook" <keescook@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
"Linux Containers" <containers@lists.linux-foundation.org>,
"Mauricio Vásquez Bernal" <mauricio@kinvolk.io>,
"Tycho Andersen" <tycho@tycho.pizza>,
"Giuseppe Scrivano" <gscrivan@redhat.com>,
"Christian Brauner" <christian.brauner@ubuntu.com>
Subject: Re: [PATCH 5/5] selftests/seccomp: Add test for atomic addfd+send
Date: Thu, 18 Mar 2021 19:31:36 +0100 [thread overview]
Message-ID: <CACaBj2ZEtrcjuv_F2=ff+ewfQaxbySqSq3vfFNnf+87n15sApw@mail.gmail.com> (raw)
In-Reply-To: <20210318051733.2544-6-sargun@sargun.me>
On Thu, Mar 18, 2021 at 6:17 AM Sargun Dhillon <sargun@sargun.me> wrote:
>
> This just adds a test to verify that when using the new introduced flag
> to ADDFD, a valid fd is added and returned as the syscall result.
>
> Signed-off-by: Rodrigo Campos <rodrigo@kinvolk.io>
> Signed-off-by: Sargun Dhillon <sargun@sargun.me>
I think in the last minutes changes this was removed by mistake:
From: Rodrigo Campos <rodrigo@kinvolk.io>
I'm happy to add more tests if we decide to merge patch 4 :)
prev parent reply other threads:[~2021-03-18 18:34 UTC|newest]
Thread overview: 8+ 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-18 5:17 ` [PATCH 1/5] seccomp: Refactor notification handler to prepare for new semantics Sargun Dhillon
2021-04-13 16:07 ` Rodrigo Campos
2021-03-18 5:17 ` [PATCH 2/5] seccomp: Add wait_killable semantic to seccomp user notifier Sargun Dhillon
2021-03-18 5:17 ` [PATCH 3/5] selftests/seccomp: Add test for wait killable notifier Sargun Dhillon
2021-03-18 5:17 ` [PATCH 4/5] seccomp: Support atomic "addfd + send reply" Sargun Dhillon
2021-03-18 5:17 ` [PATCH 5/5] selftests/seccomp: Add test for atomic addfd+send Sargun Dhillon
2021-03-18 18:31 ` Rodrigo Campos [this message]
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='CACaBj2ZEtrcjuv_F2=ff+ewfQaxbySqSq3vfFNnf+87n15sApw@mail.gmail.com' \
--to=rodrigo@kinvolk.io \
--cc=christian.brauner@ubuntu.com \
--cc=containers@lists.linux-foundation.org \
--cc=gscrivan@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mauricio@kinvolk.io \
--cc=sargun@sargun.me \
--cc=tycho@tycho.pizza \
/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).