From: patchwork-bot+netdevbpf@kernel.org
To: Yauheni Kaliuta <ykaliuta@redhat.com>
Cc: bpf@vger.kernel.org, andrii@kernel.org,
alexei.starovoitov@gmail.com, jbenc@redhat.com,
daniel@iogearbox.net, serge@hallyn.com,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpf: use bpf_capable() instead of CAP_SYS_ADMIN for blinding decision
Date: Fri, 16 Sep 2022 20:20:15 +0000 [thread overview]
Message-ID: <166335961587.27465.6441988777317672518.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220905090149.61221-1-ykaliuta@redhat.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Mon, 5 Sep 2022 12:01:49 +0300 you wrote:
> The full CAP_SYS_ADMIN requirement for blining looks too strict
> nowadays. These days given unpriv eBPF is disabled by default, the
> main users for constant blinding coming from unpriv in particular
> via cBPF -> eBPF migration (e.g. old-style socket filters).
>
> Discussion: https://lore.kernel.org/bpf/20220831090655.156434-1-ykaliuta@redhat.com/
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: use bpf_capable() instead of CAP_SYS_ADMIN for blinding decision
https://git.kernel.org/bpf/bpf-next/c/bfeb7e399bac
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-09-16 20:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 9:06 [RFC PATCH] bpf: use bpf_capable() instead of CAP_SYS_ADMIN for blinding decision Yauheni Kaliuta
2022-08-31 15:24 ` [RFC PATCH v2] " Yauheni Kaliuta
2022-08-31 18:50 ` Serge E. Hallyn
2022-08-31 21:15 ` Daniel Borkmann
2022-09-05 9:01 ` [PATCH bpf-next] " Yauheni Kaliuta
2022-09-16 20:20 ` patchwork-bot+netdevbpf [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=166335961587.27465.6441988777317672518.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jbenc@redhat.com \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=ykaliuta@redhat.com \
/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