From: patchwork-bot+netdevbpf@kernel.org
To: Mariusz Dudek <mariusz.dudek@gmail.com>
Cc: andrii.nakryiko@gmail.com, magnus.karlsson@intel.com,
bjorn.topel@intel.com, ast@kernel.org, daniel@iogearbox.net,
netdev@vger.kernel.org, jonathan.lemon@gmail.com,
bpf@vger.kernel.org, mariuszx.dudek@intel.com
Subject: Re: [PATCH v6 bpf-next 0/2] libbpf: add support for privileged/unprivileged control separation
Date: Wed, 02 Dec 2020 23:10:07 +0000 [thread overview]
Message-ID: <160695060728.8525.8161463786281779018.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201202103923.12447-1-mariuszx.dudek@intel.com>
Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Wed, 2 Dec 2020 11:39:21 +0100 you wrote:
> From: Mariusz Dudek <mariuszx.dudek@intel.com>
>
> This patch series adds support for separation of eBPF program
> load and xsk socket creation. In for example a Kubernetes
> environment you can have an AF_XDP CNI or daemonset that is
> responsible for launching pods that execute an application
> using AF_XDP sockets. It is desirable that the pod runs with
> as low privileges as possible, CAP_NET_RAW in this case,
> and that all operations that require privileges are contained
> in the CNI or daemonset.
>
> [...]
Here is the summary with links:
- [v6,bpf-next,1/2] libbpf: separate XDP program load with xsk socket creation
https://git.kernel.org/bpf/bpf-next/c/56ab028af72b
- [v6,bpf-next,2/2] samples/bpf: sample application for eBPF load and socket creation split
https://git.kernel.org/bpf/bpf-next/c/d6482b4367ac
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:[~2020-12-02 23:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 10:39 [PATCH v6 bpf-next 0/2] libbpf: add support for privileged/unprivileged control separation mariusz.dudek
2020-12-02 10:39 ` [PATCH v6 bpf-next 1/2] libbpf: separate XDP program load with xsk socket creation mariusz.dudek
2020-12-02 10:39 ` [PATCH v6 bpf-next 2/2] samples/bpf: sample application for eBPF load and socket creation split mariusz.dudek
2020-12-03 2:50 ` Alexei Starovoitov
2020-12-03 6:54 ` Mariusz Dudek
2020-12-02 23:04 ` [PATCH v6 bpf-next 0/2] libbpf: add support for privileged/unprivileged control separation Andrii Nakryiko
2020-12-02 23:10 ` 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=160695060728.8525.8161463786281779018.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bjorn.topel@intel.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jonathan.lemon@gmail.com \
--cc=magnus.karlsson@intel.com \
--cc=mariusz.dudek@gmail.com \
--cc=mariuszx.dudek@intel.com \
--cc=netdev@vger.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.