From: Florian Westphal <fw@strlen.de>
To: <bpf@vger.kernel.org>
Cc: andrii.nakryiko@gmail.com, ast@kernel.org,
<netdev@vger.kernel.org>,
dxu@dxuuu.xyz, qde@naccy.de, Florian Westphal <fw@strlen.de>
Subject: [PATCH bpf-next 0/2] libbpf: add netfilter link attach helper
Date: Thu, 25 May 2023 13:00:58 +0200 [thread overview]
Message-ID: <20230525110100.8212-1-fw@strlen.de> (raw)
When initial netfilter bpf program type support got added one
suggestion was to extend libbpf with a helper to ease attachment
of nf programs to the hook locations.
Add such a helper and a demo test case that attaches a dummy
program to various combinations.
I tested that the selftest fails when changing the expected
outcome (i.e., set 'success' when it should fail and v.v.).
Florian Westphal (2):
tools: libbpf: add netfilter link attach helper
selftests/bpf: Add bpf_program__attach_netfilter_opts helper test
tools/lib/bpf/libbpf.c | 51 +++++++++++
tools/lib/bpf/libbpf.h | 15 ++++
tools/lib/bpf/libbpf.map | 1 +
.../bpf/prog_tests/netfilter_basic.c | 87 +++++++++++++++++++
.../bpf/progs/test_netfilter_link_attach.c | 14 +++
5 files changed, 168 insertions(+)
create mode 100644 tools/testing/selftests/bpf/prog_tests/netfilter_basic.c
create mode 100644 tools/testing/selftests/bpf/progs/test_netfilter_link_attach.c
--
2.39.3
next reply other threads:[~2023-05-25 11:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 11:00 Florian Westphal [this message]
2023-05-25 11:00 ` [PATCH bpf-next 1/2] tools: libbpf: add netfilter link attach helper Florian Westphal
2023-05-25 21:01 ` Andrii Nakryiko
2023-05-26 12:11 ` [PATCH bpf] bpf: netfilter: add BPF_NETFILTER bpf_attach_type Florian Westphal
2023-05-30 17:10 ` Andrii Nakryiko
2023-05-25 11:01 ` [PATCH bpf-next 2/2] selftests/bpf: Add bpf_program__attach_netfilter_opts helper test Florian Westphal
2023-05-25 21:05 ` Andrii Nakryiko
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=20230525110100.8212-1-fw@strlen.de \
--to=fw@strlen.de \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dxu@dxuuu.xyz \
--cc=netdev@vger.kernel.org \
--cc=qde@naccy.de \
/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;
as well as URLs for NNTP newsgroup(s).