tools/testing/selftests/bpf/prog_tests/netfilter_link_attach.c
Source file repositories/reference/linux-study-clean/tools/testing/selftests/bpf/prog_tests/netfilter_link_attach.c
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/bpf/prog_tests/netfilter_link_attach.c- Extension
.c- Size
- 3360 bytes
- Lines
- 125
- Domain
- Support Tooling And Documentation
- Bucket
- tools
- Inferred role
- Support Tooling And Documentation: implementation source
- Status
- source implementation candidate
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
netinet/in.hlinux/netfilter.htest_progs.htest_netfilter_link_attach.skel.h
Detected Declarations
struct nf_link_testfunction verify_netfilter_link_infofunction test_netfilter_link_attach
Annotated Snippet
struct nf_link_test {
__u32 pf;
__u32 hooknum;
__s32 priority;
__u32 flags;
bool expect_success;
const char * const name;
};
static const struct nf_link_test nf_hook_link_tests[] = {
{ .name = "allzero", },
{ .pf = NFPROTO_NUMPROTO, .name = "invalid-pf", },
{ .pf = NFPROTO_IPV4, .hooknum = 42, .name = "invalid-hooknum", },
{ .pf = NFPROTO_IPV4, .priority = INT_MIN, .name = "invalid-priority-min", },
{ .pf = NFPROTO_IPV4, .priority = INT_MAX, .name = "invalid-priority-max", },
{ .pf = NFPROTO_IPV4, .flags = UINT_MAX, .name = "invalid-flags", },
{ .pf = NFPROTO_INET, .priority = 1, .name = "invalid-inet-not-supported", },
{
.pf = NFPROTO_IPV4,
.hooknum = NF_INET_POST_ROUTING,
.priority = -10000,
.flags = 0,
.expect_success = true,
.name = "attach ipv4",
},
{
.pf = NFPROTO_IPV6,
.hooknum = NF_INET_FORWARD,
.priority = 10001,
.flags = BPF_F_NETFILTER_IP_DEFRAG,
.expect_success = true,
.name = "attach ipv6",
},
};
static void verify_netfilter_link_info(struct bpf_link *link, const struct nf_link_test nf_expected)
{
struct bpf_link_info info;
__u32 len = sizeof(info);
int err, fd;
memset(&info, 0, len);
fd = bpf_link__fd(link);
err = bpf_link_get_info_by_fd(fd, &info, &len);
ASSERT_OK(err, "get_link_info");
ASSERT_EQ(info.type, BPF_LINK_TYPE_NETFILTER, "info link type");
ASSERT_EQ(info.netfilter.pf, nf_expected.pf, "info nf protocol family");
ASSERT_EQ(info.netfilter.hooknum, nf_expected.hooknum, "info nf hooknum");
ASSERT_EQ(info.netfilter.priority, nf_expected.priority, "info nf priority");
ASSERT_EQ(info.netfilter.flags, nf_expected.flags, "info nf flags");
}
void test_netfilter_link_attach(void)
{
struct test_netfilter_link_attach *skel;
struct bpf_program *prog;
LIBBPF_OPTS(bpf_netfilter_opts, opts);
int i;
skel = test_netfilter_link_attach__open_and_load();
if (!ASSERT_OK_PTR(skel, "test_netfilter_link_attach__open_and_load"))
goto out;
prog = skel->progs.nf_link_attach_test;
if (!ASSERT_OK_PTR(prog, "attach program"))
goto out;
for (i = 0; i < ARRAY_SIZE(nf_hook_link_tests); i++) {
struct bpf_link *link;
if (!test__start_subtest(nf_hook_link_tests[i].name))
continue;
#define X(opts, m, i) opts.m = nf_hook_link_tests[(i)].m
X(opts, pf, i);
X(opts, hooknum, i);
X(opts, priority, i);
X(opts, flags, i);
#undef X
link = bpf_program__attach_netfilter(prog, &opts);
if (nf_hook_link_tests[i].expect_success) {
struct bpf_link *link2;
if (!ASSERT_OK_PTR(link, "program attach successful"))
continue;
Annotation
- Immediate include surface: `netinet/in.h`, `linux/netfilter.h`, `test_progs.h`, `test_netfilter_link_attach.skel.h`.
- Detected declarations: `struct nf_link_test`, `function verify_netfilter_link_info`, `function test_netfilter_link_attach`.
- Atlas domain: Support Tooling And Documentation / tools.
- Implementation status: source implementation candidate.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.