From: patchwork-bot+netdevbpf@kernel.org
To: Mahe Tardy <mahe.tardy@gmail.com>
Cc: bpf@vger.kernel.org, andrew+netdev@lunn.ch, andrii@kernel.org,
ast@kernel.org, daniel@iogearbox.net, davem@davemloft.net,
eddyz87@gmail.com, edumazet@google.com, john.fastabend@gmail.com,
kuba@kernel.org, liamwisehart@meta.com, martin.lau@linux.dev,
pabeni@redhat.com, song@kernel.org, netdev@vger.kernel.org,
sdf.kernel@gmail.com, ameryhung@gmail.com, kuniyu@google.com,
memxor@gmail.com, jiayuan.chen@linux.dev
Subject: Re: [PATCH bpf-next v7 0/5] Introduce bpf_ksock
Date: Sat, 15 Aug 2026 21:40:16 +0000 [thread overview]
Message-ID: <178683001639.93126.16574683717755052782.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260813110540.103550-1-mahe.tardy@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 13 Aug 2026 11:05:35 +0000 you wrote:
> This patch series introduces bpf_ksock, a set of BPF kfuncs to allow BPF
> programs to create UDP sockets and send data. This provides a mechanism
> for BPF LSM progs to emit telemetry over UDP independently of userspace.
>
> The main use case is to be able to completely dispense with
> agents/daemons for BPF programs after startup. In the case of
> Isovalent's Tetragon, the idea would be to be able to emit security
> alerts or export data from BPF even when the agent is down. For meta,
> according to Liam presentation[^2], this could replace logging via
> ringbuffers which created cross-binary versioning issues.
>
> [...]
Here is the summary with links:
- [bpf-next,v7,1/5] net: Add connect_socket() helper
(no matching commit)
- [bpf-next,v7,2/5] bpf: Add ksock kfuncs
(no matching commit)
- [bpf-next,v7,3/5] selftests/bpf: Add ksock kfunc test
https://git.kernel.org/bpf/bpf-next/c/c7838e3dc61a
- [bpf-next,v7,4/5] selftests/bpf: Test forbidden bpf_ksock_send() LSM attach
(no matching commit)
- [bpf-next,v7,5/5] selftests/bpf: Add ksock test for async callback guard
https://git.kernel.org/bpf/bpf-next/c/c93cbdb13f99
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:[~2026-08-15 21:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 11:05 [PATCH bpf-next v7 0/5] Introduce bpf_ksock Mahe Tardy
2026-08-13 11:05 ` [PATCH bpf-next v7 1/5] net: Add connect_socket() helper Mahe Tardy
2026-08-13 11:05 ` [PATCH bpf-next v7 2/5] bpf: Add ksock kfuncs Mahe Tardy
2026-08-13 11:05 ` [PATCH bpf-next v7 3/5] selftests/bpf: Add ksock kfunc test Mahe Tardy
2026-08-13 12:13 ` bot+bpf-ci
2026-08-14 16:59 ` Mahe Tardy
2026-08-13 11:05 ` [PATCH bpf-next v7 4/5] selftests/bpf: Test forbidden bpf_ksock_send() LSM attach Mahe Tardy
2026-08-13 11:05 ` [PATCH bpf-next v7 5/5] selftests/bpf: Add ksock test for async callback guard Mahe Tardy
2026-08-13 12:13 ` bot+bpf-ci
2026-08-14 17:02 ` Mahe Tardy
2026-08-15 21:40 ` 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=178683001639.93126.16574683717755052782.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ameryhung@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=eddyz87@gmail.com \
--cc=edumazet@google.com \
--cc=jiayuan.chen@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=liamwisehart@meta.com \
--cc=mahe.tardy@gmail.com \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf.kernel@gmail.com \
--cc=song@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.