From: Jakub Kicinski <kuba@kernel.org>
To: torvalds@linuxfoundation.org
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
daniel@iogearbox.net, andrii@kernel.org, peterz@infradead.org,
brauner@kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org,
kernel-team@fb.com, linux-kernel@vger.kernel.org
Subject: Re: pull-request: bpf-next 2023-12-18
Date: Mon, 18 Dec 2023 16:55:13 -0800 [thread overview]
Message-ID: <20231218165513.24717ec1@kernel.org> (raw)
In-Reply-To: <20231219000520.34178-1-alexei.starovoitov@gmail.com>
On Mon, 18 Dec 2023 16:05:20 -0800 Alexei Starovoitov wrote:
> 2) Introduce BPF token object, from Andrii Nakryiko.
> It adds an ability to delegate a subset of BPF features from privileged daemon
> (e.g., systemd) through special mount options for userns-bound BPF FS to a
> trusted unprivileged application. The design accommodates suggestions from
> Christian Brauner and Paul Moore.
> Example:
> $ sudo mkdir -p /sys/fs/bpf/token
> $ sudo mount -t bpf bpffs /sys/fs/bpf/token \
> -o delegate_cmds=prog_load:MAP_CREATE \
> -o delegate_progs=kprobe \
> -o delegate_attachs=xdp
LGTM, but what do I know about file systems.. Adding LKML to the CC
list, if anyone has any late comments on the BPF token come forward
now, petty please?
next prev parent reply other threads:[~2023-12-19 0:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 0:05 pull-request: bpf-next 2023-12-18 Alexei Starovoitov
2023-12-19 0:19 ` Alexei Starovoitov
2023-12-19 0:55 ` Jakub Kicinski [this message]
2023-12-19 1:17 ` Linus Torvalds
2023-12-19 1:10 ` patchwork-bot+netdevbpf
2023-12-19 1:11 ` Linus Torvalds
2023-12-19 1:48 ` Alexei Starovoitov
2023-12-19 3:57 ` Linus Torvalds
2023-12-19 4:34 ` Andrii Nakryiko
2023-12-19 5:38 ` Andrii Nakryiko
2023-12-19 10:23 ` Christian Brauner
2023-12-19 16:06 ` Matthew Wilcox
2023-12-19 16:51 ` Alexei Starovoitov
2023-12-19 16:36 ` Daniel Borkmann
2023-12-19 16:42 ` Alexei Starovoitov
2023-12-19 18:31 ` Andrii Nakryiko
2023-12-20 11:18 ` Christian Brauner
2023-12-20 19:17 ` Andrii Nakryiko
2023-12-21 13:05 ` Christian Brauner
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=20231218165513.24717ec1@kernel.org \
--to=kuba@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peterz@infradead.org \
--cc=torvalds@linuxfoundation.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.