From: "Mickaël Salaün" <mic@digikod.net>
To: Kees Cook <keescook@chromium.org>, Shuah Khan <shuah@kernel.org>
Cc: "Mickaël Salaün" <mic@digikod.net>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
"Mickaël Salaün" <mic@linux.microsoft.com>,
"Tycho Andersen" <tycho@tycho.pizza>
Subject: [PATCH] selftests/seccomp: Update kernel config
Date: Wed, 2 Dec 2020 17:26:43 +0100 [thread overview]
Message-ID: <20201202162643.249276-1-mic@digikod.net> (raw)
From: Mickaël Salaün <mic@linux.microsoft.com>
seccomp_bpf.c uses unshare(CLONE_NEWPID), which requires CONFIG_PID_NS
to be set.
Cc: Kees Cook <keescook@chromium.org>
Cc: Shuah Khan <shuah@kernel.org>
Fixes: 6a21cc50f0c7 ("seccomp: add a return code to trap to userspace")
Signed-off-by: Mickaël Salaün <mic@linux.microsoft.com>
Acked-by: Tycho Andersen <tycho@tycho.pizza>
---
Previous version:
https://lore.kernel.org/lkml/20201030121819.764395-1-mic@digikod.net/
Changes since v1:
* Add Acked-by: Tycho Andersen <tycho@tycho.pizza>
* Synchronize From and Signed-off-by emails.
---
tools/testing/selftests/seccomp/config | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/seccomp/config b/tools/testing/selftests/seccomp/config
index 64c19d8eba79..ad431a5178fb 100644
--- a/tools/testing/selftests/seccomp/config
+++ b/tools/testing/selftests/seccomp/config
@@ -1,3 +1,4 @@
+CONFIG_PID_NS=y
CONFIG_SECCOMP=y
CONFIG_SECCOMP_FILTER=y
CONFIG_USER_NS=y
base-commit: b65054597872ce3aefbc6a666385eabdf9e288da
--
2.29.2
next reply other threads:[~2020-12-02 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 16:26 Mickaël Salaün [this message]
2020-12-02 19:22 ` [PATCH] selftests/seccomp: Update kernel config Kees Cook
-- strict thread matches above, loose matches on Subject: below --
2020-10-30 12:18 Mickaël Salaün
2020-11-10 21:36 ` Shuah Khan
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=20201202162643.249276-1-mic@digikod.net \
--to=mic@digikod.net \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mic@linux.microsoft.com \
--cc=shuah@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.