BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Sitnicki <jakub@cloudflare.com>
Cc: bpf@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	martin.lau@linux.dev, daniel@iogearbox.net,
	john.fastabend@gmail.com, sdf@fomichev.me, ast@kernel.org,
	andrii@kernel.org, eddyz87@gmail.com, song@kernel.org,
	yonghong.song@linux.dev, kpsingh@kernel.org, haoluo@google.com,
	jolsa@kernel.org, arthur@arthurfabre.com, hawk@kernel.org,
	netdev@vger.kernel.org, kernel-team@cloudflare.com
Subject: Re: [PATCH bpf-next v4 00/16] Make TC BPF helpers preserve skb metadata
Date: Mon, 10 Nov 2025 19:30:01 +0000	[thread overview]
Message-ID: <176280300126.2739595.12327410423066489915.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251105-skb-meta-rx-path-v4-0-5ceb08a9b37b@cloudflare.com>

Hello:

This series was applied to bpf/bpf-next.git (net)
by Martin KaFai Lau <martin.lau@kernel.org>:

On Wed, 05 Nov 2025 21:19:37 +0100 you wrote:
> Changes in v4:
> - Fix copy-paste bug in check_metadata() test helper (AI review)
> - Add "out of scope" section (at the bottom)
> - Link to v3: https://lore.kernel.org/r/20251026-skb-meta-rx-path-v3-0-37cceebb95d3@cloudflare.com
> 
> Changes in v3:
> - Use the already existing BPF_STREAM_STDERR const in tests (Martin)
> - Unclone skb head on bpf_dynptr_write to skb metadata (patch 3) (Martin)
> - Swap order of patches 1 & 2 to refer to skb_postpush_data_move() in docs
> - Mention in skb_data_move() docs how to move just the metadata
> - Note in pskb_expand_head() docs to move metadata after skb_push() (Jakub)
> - Link to v2: https://lore.kernel.org/r/20251019-skb-meta-rx-path-v2-0-f9a58f3eb6d6@cloudflare.com
> 
> [...]

Here is the summary with links:
  - [bpf-next,v4,01/16] net: Helper to move packet data and metadata after skb_push/pull
    https://git.kernel.org/bpf/bpf-next/c/8989d328dfe7
  - [bpf-next,v4,02/16] net: Preserve metadata on pskb_expand_head
    https://git.kernel.org/bpf/bpf-next/c/290fc0be09e2
  - [bpf-next,v4,03/16] bpf: Unclone skb head on bpf_dynptr_write to skb metadata
    https://git.kernel.org/bpf/bpf-next/c/f38499ff45f5
  - [bpf-next,v4,04/16] vlan: Make vlan_remove_tag return nothing
    https://git.kernel.org/bpf/bpf-next/c/b85be58e2f7c
  - [bpf-next,v4,05/16] bpf: Make bpf_skb_vlan_pop helper metadata-safe
    https://git.kernel.org/bpf/bpf-next/c/efd35c26239b
  - [bpf-next,v4,06/16] bpf: Make bpf_skb_vlan_push helper metadata-safe
    https://git.kernel.org/bpf/bpf-next/c/55ffc98b44d2
  - [bpf-next,v4,07/16] bpf: Make bpf_skb_adjust_room metadata-safe
    https://git.kernel.org/bpf/bpf-next/c/be83105d38ab
  - [bpf-next,v4,08/16] bpf: Make bpf_skb_change_proto helper metadata-safe
    https://git.kernel.org/bpf/bpf-next/c/8cfc172ce28e
  - [bpf-next,v4,09/16] bpf: Make bpf_skb_change_head helper metadata-safe
    https://git.kernel.org/bpf/bpf-next/c/fb206fc3129b
  - [bpf-next,v4,10/16] selftests/bpf: Verify skb metadata in BPF instead of userspace
    https://git.kernel.org/bpf/bpf-next/c/967534e57c44
  - [bpf-next,v4,11/16] selftests/bpf: Dump skb metadata on verification failure
    https://git.kernel.org/bpf/bpf-next/c/9ef9ac15a527
  - [bpf-next,v4,12/16] selftests/bpf: Expect unclone to preserve skb metadata
    https://git.kernel.org/bpf/bpf-next/c/1e1357fde808
  - [bpf-next,v4,13/16] selftests/bpf: Cover skb metadata access after vlan push/pop helper
    https://git.kernel.org/bpf/bpf-next/c/354d020c29f7
  - [bpf-next,v4,14/16] selftests/bpf: Cover skb metadata access after bpf_skb_adjust_room
    https://git.kernel.org/bpf/bpf-next/c/29960e635b01
  - [bpf-next,v4,15/16] selftests/bpf: Cover skb metadata access after change_head/tail helper
    https://git.kernel.org/bpf/bpf-next/c/85d454afef61
  - [bpf-next,v4,16/16] selftests/bpf: Cover skb metadata access after bpf_skb_change_proto
    https://git.kernel.org/bpf/bpf-next/c/d2c5cca3fb58

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



      parent reply	other threads:[~2025-11-10 19:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05 20:19 [PATCH bpf-next v4 00/16] Make TC BPF helpers preserve skb metadata Jakub Sitnicki
2025-11-05 20:19 ` [PATCH bpf-next v4 01/16] net: Helper to move packet data and metadata after skb_push/pull Jakub Sitnicki
2025-11-05 20:19 ` [PATCH bpf-next v4 02/16] net: Preserve metadata on pskb_expand_head Jakub Sitnicki
2025-11-05 20:19 ` [PATCH bpf-next v4 03/16] bpf: Unclone skb head on bpf_dynptr_write to skb metadata Jakub Sitnicki
2025-11-05 20:19 ` [PATCH bpf-next v4 04/16] vlan: Make vlan_remove_tag return nothing Jakub Sitnicki
2025-11-05 20:19 ` [PATCH bpf-next v4 05/16] bpf: Make bpf_skb_vlan_pop helper metadata-safe Jakub Sitnicki
2025-11-05 20:19 ` [PATCH bpf-next v4 06/16] bpf: Make bpf_skb_vlan_push " Jakub Sitnicki
2025-11-05 20:19 ` [PATCH bpf-next v4 07/16] bpf: Make bpf_skb_adjust_room metadata-safe Jakub Sitnicki
2025-11-05 20:42   ` bot+bpf-ci
2025-11-10 12:17     ` Jakub Sitnicki
2025-11-05 20:19 ` [PATCH bpf-next v4 08/16] bpf: Make bpf_skb_change_proto helper metadata-safe Jakub Sitnicki
2025-11-05 20:19 ` [PATCH bpf-next v4 09/16] bpf: Make bpf_skb_change_head " Jakub Sitnicki
2025-11-05 20:19 ` [PATCH bpf-next v4 10/16] selftests/bpf: Verify skb metadata in BPF instead of userspace Jakub Sitnicki
2025-11-05 20:19 ` [PATCH bpf-next v4 11/16] selftests/bpf: Dump skb metadata on verification failure Jakub Sitnicki
2025-11-05 20:19 ` [PATCH bpf-next v4 12/16] selftests/bpf: Expect unclone to preserve skb metadata Jakub Sitnicki
2025-11-05 20:19 ` [PATCH bpf-next v4 13/16] selftests/bpf: Cover skb metadata access after vlan push/pop helper Jakub Sitnicki
2025-11-05 20:19 ` [PATCH bpf-next v4 14/16] selftests/bpf: Cover skb metadata access after bpf_skb_adjust_room Jakub Sitnicki
2025-11-05 20:19 ` [PATCH bpf-next v4 15/16] selftests/bpf: Cover skb metadata access after change_head/tail helper Jakub Sitnicki
2025-11-05 20:19 ` [PATCH bpf-next v4 16/16] selftests/bpf: Cover skb metadata access after bpf_skb_change_proto Jakub Sitnicki
2025-11-10 19:30 ` 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=176280300126.2739595.12327410423066489915.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=arthur@arthurfabre.com \
    --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=haoluo@google.com \
    --cc=hawk@kernel.org \
    --cc=horms@kernel.org \
    --cc=jakub@cloudflare.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kernel-team@cloudflare.com \
    --cc=kpsingh@kernel.org \
    --cc=kuba@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    --cc=song@kernel.org \
    --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