From: patchwork-bot+netdevbpf@kernel.org
To: Hudson@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
Nick <nhudson@akamai.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, willemb@google.com,
martin.lau@linux.dev, mtottenh@akamai.com, aglasgal@akamai.com
Subject: Re: [PATCH bpf-next v7 0/6] bpf: decap flags and GSO state updates
Date: Mon, 17 Aug 2026 09:40:33 +0000 [thread overview]
Message-ID: <178695963358.1043070.9614982598218291426.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260812083115.73100-1-nhudson@akamai.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 12 Aug 2026 09:31:09 +0100 you wrote:
> This series extends bpf_skb_adjust_room() with decapsulation-specific
> flags and tunnel GSO state updates for decap use cases.
>
> Motivation
> ----------
>
> When BPF decapsulates tunneled packets, skb GSO state needs to be
> updated to match the removed tunnel layer. This includes clearing the
> corresponding tunnel GSO type bits and resetting encapsulation state
> once no tunnel GSO flags remain.
>
> [...]
Here is the summary with links:
- [bpf-next,v7,1/6] bpf: name the enum for BPF_FUNC_skb_adjust_room flags
https://git.kernel.org/bpf/bpf-next/c/5e4bcad6171d
- [bpf-next,v7,2/6] bpf: refactor masks for ADJ_ROOM flags and encap validation
https://git.kernel.org/bpf/bpf-next/c/7b2ea1151e04
- [bpf-next,v7,3/6] bpf: add BPF_F_ADJ_ROOM_DECAP_* flags for tunnel decapsulation
https://git.kernel.org/bpf/bpf-next/c/da199070bc62
- [bpf-next,v7,4/6] bpf: allow new DECAP flags and add guard rails
https://git.kernel.org/bpf/bpf-next/c/3a39c214fd2c
- [bpf-next,v7,5/6] bpf: clear decap state on skb_adjust_room shrink path
https://git.kernel.org/bpf/bpf-next/c/ec20dee2f2c4
- [bpf-next,v7,6/6] selftests/bpf: tc_tunnel - validate decap GSO and encapsulation state
https://git.kernel.org/bpf/bpf-next/c/adb771973026
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-17 9:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 8:31 [PATCH bpf-next v7 0/6] bpf: decap flags and GSO state updates Nick Hudson
2026-08-12 8:31 ` [PATCH bpf-next v7 1/6] bpf: name the enum for BPF_FUNC_skb_adjust_room flags Nick Hudson
2026-08-12 8:31 ` [PATCH bpf-next v7 2/6] bpf: refactor masks for ADJ_ROOM flags and encap validation Nick Hudson
2026-08-12 10:33 ` bot+bpf-ci
2026-08-14 8:40 ` Hudson, Nick
2026-08-12 8:31 ` [PATCH bpf-next v7 3/6] bpf: add BPF_F_ADJ_ROOM_DECAP_* flags for tunnel decapsulation Nick Hudson
2026-08-12 8:31 ` [PATCH bpf-next v7 4/6] bpf: allow new DECAP flags and add guard rails Nick Hudson
2026-08-12 10:22 ` sashiko-bot
2026-08-12 12:13 ` Hudson, Nick
2026-08-12 10:33 ` bot+bpf-ci
2026-08-12 8:31 ` [PATCH bpf-next v7 5/6] bpf: clear decap state on skb_adjust_room shrink path Nick Hudson
2026-08-12 10:26 ` sashiko-bot
2026-08-12 12:30 ` Hudson, Nick
2026-08-12 10:33 ` bot+bpf-ci
2026-08-14 8:33 ` Hudson, Nick
2026-08-12 8:31 ` [PATCH bpf-next v7 6/6] selftests/bpf: tc_tunnel - validate decap GSO and encapsulation state Nick Hudson
2026-08-12 10:20 ` sashiko-bot
2026-08-12 12:23 ` Hudson, Nick
2026-08-12 10:48 ` bot+bpf-ci
2026-08-17 9: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=178695963358.1043070.9614982598218291426.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Hudson@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=aglasgal@akamai.com \
--cc=bpf@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mtottenh@akamai.com \
--cc=netdev@vger.kernel.org \
--cc=nhudson@akamai.com \
--cc=willemb@google.com \
/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