BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, ast@kernel.org,
	daniel@iogearbox.net, john.fastabend@gmail.com, sdf@fomichev.me,
	willemb@google.com
Subject: Re: [PATCH bpf v3 0/2] support SKF_NET_OFF and SKF_LL_OFF on skb frags
Date: Thu, 10 Apr 2025 03:10:33 +0000	[thread overview]
Message-ID: <174425463347.3131897.8400985882476107728.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250408132833.195491-1-willemdebruijn.kernel@gmail.com>

Hello:

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

On Tue,  8 Apr 2025 09:27:47 -0400 you wrote:
> From: Willem de Bruijn <willemb@google.com>
> 
> Address a longstanding issue that may lead to missed packets
> depending on system configuration.
> 
> Ensure that reading from packet contents works regardless of skb
> geometry, also when using the special SKF_.. negative offsets to
> offset from L2 or L3 header.
> 
> [...]

Here is the summary with links:
  - [bpf,v3,1/2] bpf: support SKF_NET_OFF and SKF_LL_OFF on skb frags
    https://git.kernel.org/bpf/bpf/c/d4bac0288a2b
  - [bpf,v3,2/2] selftests/net: test sk_filter support for SKF_NET_OFF on frags
    https://git.kernel.org/bpf/bpf/c/fcd7132cb1f9

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-04-10  3:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 13:27 [PATCH bpf v3 0/2] support SKF_NET_OFF and SKF_LL_OFF on skb frags Willem de Bruijn
2025-04-08 13:27 ` [PATCH bpf v3 1/2] bpf: " Willem de Bruijn
2025-04-09 14:05   ` Stanislav Fomichev
2025-04-08 13:27 ` [PATCH bpf v3 2/2] selftests/net: test sk_filter support for SKF_NET_OFF on frags Willem de Bruijn
2025-04-10  3:10 ` 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=174425463347.3131897.8400985882476107728.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=john.fastabend@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=sdf@fomichev.me \
    --cc=willemb@google.com \
    --cc=willemdebruijn.kernel@gmail.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