From: Daniel Borkmann <daniel@iogearbox.net>
To: "Mickaël Salaün" <mic@digikod.net>, linux-kernel@vger.kernel.org
Cc: Alexei Starovoitov <ast@fb.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
"David S . Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH net-next v2 3/3] bpf: Always test unprivileged programs
Date: Mon, 06 Feb 2017 23:44:58 +0100 [thread overview]
Message-ID: <5898FC6A.5020505@iogearbox.net> (raw)
In-Reply-To: <20170206205225.32233-3-mic@digikod.net>
On 02/06/2017 09:52 PM, Mickaël Salaün wrote:
> If selftests are run as root, then execute the unprivileged checks as
> well. This switch from 240 to 364 tests.
>
> The test numbers are suffixed with "/u" when executed as unprivileged or
> with "/p" when executed as privileged.
>
> The geteuid() check is replaced with a capability check.
>
> Handling capabilities requires the libcap dependency.
>
> Signed-off-by: Mickaël Salaün <mic@digikod.net>
> Cc: Alexei Starovoitov <ast@fb.com>
> Cc: Daniel Borkmann <daniel@iogearbox.net>
> Cc: Shuah Khan <shuah@kernel.org>
Acked-by: Daniel Borkmann <daniel@iogearbox.net>
next prev parent reply other threads:[~2017-02-06 22:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 20:52 [PATCH net-next v2 1/3] tools: Sync {,tools/}include/uapi/linux/bpf.h Mickaël Salaün
2017-02-06 20:52 ` [PATCH net-next v2 2/3] bpf: Change the include directory for selftest Mickaël Salaün
2017-02-06 20:52 ` [PATCH net-next v2 3/3] bpf: Always test unprivileged programs Mickaël Salaün
2017-02-06 21:19 ` Alexei Starovoitov
2017-02-06 22:44 ` Daniel Borkmann [this message]
2017-02-07 18:01 ` [PATCH net-next v2 1/3] tools: Sync {,tools/}include/uapi/linux/bpf.h David Miller
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=5898FC6A.5020505@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=acme@redhat.com \
--cc=ast@fb.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mic@digikod.net \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.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 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.