netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: linux-kernel@vger.kernel.org, coreteam@netfilter.org,
	netfilter-devel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	bpf@vger.kernel.org, netdev@vger.kernel.org,
	alexei.starovoitov@gmail.com, fw@strlen.de, daniel@iogearbox.net,
	dsahern@kernel.org
Subject: Re: [PATCH bpf-next v6 0/5] Support defragmenting IPv(4|6) packets in BPF
Date: Sat, 29 Jul 2023 00:00:23 +0000	[thread overview]
Message-ID: <169058882394.20221.4449281517467236117.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1689970773.git.dxu@dxuuu.xyz>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Fri, 21 Jul 2023 14:22:44 -0600 you wrote:
> === Context ===
> 
> In the context of a middlebox, fragmented packets are tricky to handle.
> The full 5-tuple of a packet is often only available in the first
> fragment which makes enforcing consistent policy difficult. There are
> really only two stateless options, neither of which are very nice:
> 
> [...]

Here is the summary with links:
  - [bpf-next,v6,1/5] netfilter: defrag: Add glue hooks for enabling/disabling defrag
    https://git.kernel.org/bpf/bpf-next/c/9abddac583d6
  - [bpf-next,v6,2/5] netfilter: bpf: Support BPF_F_NETFILTER_IP_DEFRAG in netfilter link
    https://git.kernel.org/bpf/bpf-next/c/91721c2d02d3
  - [bpf-next,v6,3/5] bpf: selftests: Support not connecting client socket
    https://git.kernel.org/bpf/bpf-next/c/3495e89cdc3a
  - [bpf-next,v6,4/5] bpf: selftests: Support custom type and proto for client sockets
    https://git.kernel.org/bpf/bpf-next/c/e15a22095608
  - [bpf-next,v6,5/5] bpf: selftests: Add defrag selftests
    https://git.kernel.org/bpf/bpf-next/c/c313eae739b9

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-07-29  0:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21 20:22 [PATCH bpf-next v6 0/5] Support defragmenting IPv(4|6) packets in BPF Daniel Xu
2023-07-21 20:22 ` [PATCH bpf-next v6 1/5] netfilter: defrag: Add glue hooks for enabling/disabling defrag Daniel Xu
2023-07-28  9:16   ` Florian Westphal
2023-07-21 20:22 ` [PATCH bpf-next v6 2/5] netfilter: bpf: Support BPF_F_NETFILTER_IP_DEFRAG in netfilter link Daniel Xu
2023-07-28  1:16   ` Alexei Starovoitov
2023-07-28  4:37     ` Daniel Xu
2023-07-28  9:52   ` Florian Westphal
2023-07-21 20:22 ` [PATCH bpf-next v6 3/5] bpf: selftests: Support not connecting client socket Daniel Xu
2023-07-21 20:22 ` [PATCH bpf-next v6 4/5] bpf: selftests: Support custom type and proto for client sockets Daniel Xu
2023-07-21 20:22 ` [PATCH bpf-next v6 5/5] bpf: selftests: Add defrag selftests Daniel Xu
2023-07-29  0: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=169058882394.20221.4449281517467236117.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=coreteam@netfilter.org \
    --cc=daniel@iogearbox.net \
    --cc=dsahern@kernel.org \
    --cc=dxu@dxuuu.xyz \
    --cc=fw@strlen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).