From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: bpf@vger.kernel.org
Cc: netdev@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
john.fastabend@gmail.com, Willem de Bruijn <willemb@google.com>
Subject: [PATCH bpf 0/2] support SKF_NET_OFF and SKF_LL_OFF on skb frags
Date: Thu, 3 Apr 2025 10:07:44 -0400 [thread overview]
Message-ID: <20250403140846.1268564-1-willemdebruijn.kernel@gmail.com> (raw)
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.
Patch 2 is the selftest for the fix.
Willem de Bruijn (2):
bpf: support SKF_NET_OFF and SKF_LL_OFF on skb frags
selftests/net: test sk_filter support for SKF_NET_OFF on frags
include/linux/filter.h | 3 -
kernel/bpf/core.c | 21 --
net/core/filter.c | 75 ++++---
tools/testing/selftests/net/.gitignore | 1 +
tools/testing/selftests/net/Makefile | 2 +
tools/testing/selftests/net/skf_net_off.c | 244 +++++++++++++++++++++
tools/testing/selftests/net/skf_net_off.sh | 28 +++
7 files changed, 317 insertions(+), 57 deletions(-)
create mode 100644 tools/testing/selftests/net/skf_net_off.c
create mode 100755 tools/testing/selftests/net/skf_net_off.sh
--
2.49.0.472.ge94155a9ec-goog
next reply other threads:[~2025-04-03 14:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 14:07 Willem de Bruijn [this message]
2025-04-03 14:07 ` [PATCH bpf 1/2] bpf: support SKF_NET_OFF and SKF_LL_OFF on skb frags Willem de Bruijn
2025-04-03 14:18 ` Willem de Bruijn
2025-04-03 17:21 ` Stanislav Fomichev
2025-04-03 17:27 ` Willem de Bruijn
2025-04-03 17:35 ` Stanislav Fomichev
2025-04-03 18:30 ` Maciej Żenczykowski
2025-04-03 18:54 ` Willem de Bruijn
2025-04-03 14:07 ` [PATCH bpf 2/2] selftests/net: test sk_filter support for SKF_NET_OFF on frags Willem de Bruijn
2025-04-03 17:29 ` Stanislav Fomichev
2025-04-03 18:56 ` Willem de Bruijn
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=20250403140846.1268564-1-willemdebruijn.kernel@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--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 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.