From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Sitnicki <jakub@cloudflare.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
arthur@arthurfabre.com, daniel@iogearbox.net, eddyz87@gmail.com,
edumazet@google.com, kuba@kernel.org, hawk@kernel.org,
jbrandeburg@cloudflare.com, joannelkoong@gmail.com,
lorenzo@kernel.org, martin.lau@linux.dev, thoiland@redhat.com,
yan@cloudflare.com, kernel-team@cloudflare.com,
netdev@vger.kernel.org, sdf@fomichev.me
Subject: Re: [PATCH bpf-next v7 0/9] Add a dynptr type for skb metadata for TC BPF
Date: Mon, 18 Aug 2025 20:40:48 +0000 [thread overview]
Message-ID: <175554964898.2904664.15930245053733821413.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250814-skb-metadata-thru-dynptr-v7-0-8a39e636e0fb@cloudflare.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Thu, 14 Aug 2025 11:59:26 +0200 you wrote:
> TL;DR
> -----
>
> This is the first step in an effort which aims to enable skb metadata
> access for all BPF programs which operate on an skb context.
>
> By skb metadata we mean the custom metadata area which can be allocated
> from an XDP program with the bpf_xdp_adjust_meta helper [1]. Network stack
> code accesses it using the skb_metadata_* helpers.
>
> [...]
Here is the summary with links:
- [bpf-next,v7,1/9] bpf: Add dynptr type for skb metadata
https://git.kernel.org/bpf/bpf-next/c/89d912e494f7
- [bpf-next,v7,2/9] bpf: Enable read/write access to skb metadata through a dynptr
https://git.kernel.org/bpf/bpf-next/c/6877cd392bae
- [bpf-next,v7,3/9] selftests/bpf: Cover verifier checks for skb_meta dynptr type
https://git.kernel.org/bpf/bpf-next/c/0e74eb4d57f0
- [bpf-next,v7,4/9] selftests/bpf: Pass just bpf_map to xdp_context_test helper
https://git.kernel.org/bpf/bpf-next/c/6dfd5e01e1a7
- [bpf-next,v7,5/9] selftests/bpf: Parametrize test_xdp_context_tuntap
https://git.kernel.org/bpf/bpf-next/c/dd9f6cfb4ef4
- [bpf-next,v7,6/9] selftests/bpf: Cover read access to skb metadata via dynptr
https://git.kernel.org/bpf/bpf-next/c/153f6bfd4890
- [bpf-next,v7,7/9] selftests/bpf: Cover write access to skb metadata via dynptr
https://git.kernel.org/bpf/bpf-next/c/ed9336080780
- [bpf-next,v7,8/9] selftests/bpf: Cover read/write to skb metadata at an offset
https://git.kernel.org/bpf/bpf-next/c/bd1b51b31978
- [bpf-next,v7,9/9] selftests/bpf: Cover metadata access from a modified skb clone
https://git.kernel.org/bpf/bpf-next/c/403fae59781f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-08-18 20:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 9:59 [PATCH bpf-next v7 0/9] Add a dynptr type for skb metadata for TC BPF Jakub Sitnicki
2025-08-14 9:59 ` [PATCH bpf-next v7 1/9] bpf: Add dynptr type for skb metadata Jakub Sitnicki
2025-08-14 9:59 ` [PATCH bpf-next v7 2/9] bpf: Enable read/write access to skb metadata through a dynptr Jakub Sitnicki
2025-08-14 9:59 ` [PATCH bpf-next v7 3/9] selftests/bpf: Cover verifier checks for skb_meta dynptr type Jakub Sitnicki
2025-08-14 9:59 ` [PATCH bpf-next v7 4/9] selftests/bpf: Pass just bpf_map to xdp_context_test helper Jakub Sitnicki
2025-08-14 9:59 ` [PATCH bpf-next v7 5/9] selftests/bpf: Parametrize test_xdp_context_tuntap Jakub Sitnicki
2025-08-14 9:59 ` [PATCH bpf-next v7 6/9] selftests/bpf: Cover read access to skb metadata via dynptr Jakub Sitnicki
2025-08-14 9:59 ` [PATCH bpf-next v7 7/9] selftests/bpf: Cover write " Jakub Sitnicki
2025-08-14 9:59 ` [PATCH bpf-next v7 8/9] selftests/bpf: Cover read/write to skb metadata at an offset Jakub Sitnicki
2025-08-14 9:59 ` [PATCH bpf-next v7 9/9] selftests/bpf: Cover metadata access from a modified skb clone Jakub Sitnicki
2025-08-18 20:40 ` patchwork-bot+netdevbpf [this message]
2025-08-19 10:07 ` [PATCH bpf-next v7 0/9] Add a dynptr type for skb metadata for TC BPF Jakub Sitnicki
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=175554964898.2904664.15930245053733821413.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=eddyz87@gmail.com \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=jakub@cloudflare.com \
--cc=jbrandeburg@cloudflare.com \
--cc=joannelkoong@gmail.com \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=lorenzo@kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=sdf@fomichev.me \
--cc=thoiland@redhat.com \
--cc=yan@cloudflare.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 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.