tools/testing/selftests/bpf/progs/udp_limit.c
Source file repositories/reference/linux-study-clean/tools/testing/selftests/bpf/progs/udp_limit.c
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/bpf/progs/udp_limit.c- Extension
.c- Size
- 1139 bytes
- Lines
- 60
- 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
sys/socket.hlinux/bpf.hbpf/bpf_helpers.h
Detected Declarations
function sockfunction sock_release
Annotated Snippet
SEC("cgroup/sock_create")
int sock(struct bpf_sock *ctx)
{
int *sk_storage;
if (ctx->type != SOCK_DGRAM)
return 1;
sk_storage = bpf_sk_storage_get(&sk_map, ctx, 0,
BPF_SK_STORAGE_GET_F_CREATE);
if (!sk_storage)
return 0;
*sk_storage = 0xdeadbeef;
__sync_fetch_and_add(&invocations, 1);
if (in_use > 0) {
/* BPF_CGROUP_INET_SOCK_RELEASE is _not_ called
* when we return an error from the BPF
* program!
*/
return 0;
}
__sync_fetch_and_add(&in_use, 1);
return 1;
}
SEC("cgroup/sock_release")
int sock_release(struct bpf_sock *ctx)
{
int *sk_storage;
if (ctx->type != SOCK_DGRAM)
return 1;
sk_storage = bpf_sk_storage_get(&sk_map, ctx, 0, 0);
if (!sk_storage || *sk_storage != 0xdeadbeef)
return 0;
__sync_fetch_and_add(&invocations, 1);
__sync_fetch_and_add(&in_use, -1);
return 1;
}
Annotation
- Immediate include surface: `sys/socket.h`, `linux/bpf.h`, `bpf/bpf_helpers.h`.
- Detected declarations: `function sock`, `function sock_release`.
- 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.