From: patchwork-bot+netdevbpf@kernel.org
To: Mahe Tardy <mahe.tardy@gmail.com>
Cc: bpf@vger.kernel.org, andrii@kernel.org, ast@kernel.org,
daniel@iogearbox.net, john.fastabend@gmail.com, jordan@jrife.io,
martin.lau@linux.dev, yonghong.song@linux.dev,
emil@etsalapatis.com, netdev@vger.kernel.org,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
davem@davemloft.net, horms@kernel.org, sdf.kernel@gmail.com
Subject: Re: [PATCH bpf-next v11 0/5] bpf: add icmp_send kfunc
Date: Fri, 10 Jul 2026 10:00:32 +0000 [thread overview]
Message-ID: <178367763213.156295.1145469306231918635.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260709144900.245904-1-mahe.tardy@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 9 Jul 2026 14:48:55 +0000 you wrote:
> Hello,
>
> This is v11 of adding the icmp_send kfunc, as suggested during
> LSF/MM/BPF 2025[^1]. The goal is to allow cgroup_skb programs to
> actively reject east-west traffic, similarly to what is possible to do
> with netfilter reject target. Applications can receive early feedback
> that something went wrong during the TCP handshake.
>
> [...]
Here is the summary with links:
- [bpf-next,v11,1/5] bpf: add bpf_icmp_send kfunc
(no matching commit)
- [bpf-next,v11,2/5] selftests/bpf: add bpf_icmp_send kfunc cgroup_skb tests
https://git.kernel.org/bpf/bpf-next/c/39b337a3d995
- [bpf-next,v11,3/5] selftests/bpf: add bpf_icmp_send kfunc cgroup_skb IPv6 tests
(no matching commit)
- [bpf-next,v11,4/5] selftests/bpf: add bpf_icmp_send recursion test
(no matching commit)
- [bpf-next,v11,5/5] selftests/bpf: add bpf_icmp_send no route test
(no matching commit)
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-07-10 10:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 14:48 [PATCH bpf-next v11 0/5] bpf: add icmp_send kfunc Mahe Tardy
2026-07-09 14:48 ` [PATCH bpf-next v11 1/5] bpf: add bpf_icmp_send kfunc Mahe Tardy
2026-07-10 0:12 ` Stanislav Fomichev
2026-07-09 14:48 ` [PATCH bpf-next v11 2/5] selftests/bpf: add bpf_icmp_send kfunc cgroup_skb tests Mahe Tardy
2026-07-10 0:12 ` Stanislav Fomichev
2026-07-09 14:48 ` [PATCH bpf-next v11 3/5] selftests/bpf: add bpf_icmp_send kfunc cgroup_skb IPv6 tests Mahe Tardy
2026-07-10 0:12 ` Stanislav Fomichev
2026-07-09 14:48 ` [PATCH bpf-next v11 4/5] selftests/bpf: add bpf_icmp_send recursion test Mahe Tardy
2026-07-10 0:13 ` Stanislav Fomichev
2026-07-09 14:49 ` [PATCH bpf-next v11 5/5] selftests/bpf: add bpf_icmp_send no route test Mahe Tardy
2026-07-10 0:13 ` Stanislav Fomichev
2026-07-10 10:00 ` 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=178367763213.156295.1145469306231918635.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=emil@etsalapatis.com \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=jordan@jrife.io \
--cc=kuba@kernel.org \
--cc=mahe.tardy@gmail.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf.kernel@gmail.com \
--cc=yonghong.song@linux.dev \
/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