tools/testing/selftests/bpf/progs/recvmsg4_prog.c
Source file repositories/reference/linux-study-clean/tools/testing/selftests/bpf/progs/recvmsg4_prog.c
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/bpf/progs/recvmsg4_prog.c- Extension
.c- Size
- 723 bytes
- Lines
- 41
- 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
linux/stddef.hlinux/bpf.hlinux/in.hsys/socket.hbpf/bpf_helpers.hbpf/bpf_endian.hbpf_sockopt_helpers.h
Detected Declarations
function recvmsg4_prog
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
#include <linux/stddef.h>
#include <linux/bpf.h>
#include <linux/in.h>
#include <sys/socket.h>
#include <bpf/bpf_helpers.h>
#include <bpf/bpf_endian.h>
#include <bpf_sockopt_helpers.h>
#define SERV4_IP 0xc0a801feU /* 192.168.1.254 */
#define SERV4_PORT 4040
SEC("cgroup/recvmsg4")
int recvmsg4_prog(struct bpf_sock_addr *ctx)
{
struct bpf_sock *sk;
sk = ctx->sk;
if (!sk)
return 1;
if (sk->family != AF_INET)
return 1;
if (ctx->type != SOCK_STREAM && ctx->type != SOCK_DGRAM)
return 1;
if (!get_set_sk_priority(ctx))
return 1;
ctx->user_ip4 = bpf_htonl(SERV4_IP);
ctx->user_port = bpf_htons(SERV4_PORT);
return 1;
}
char _license[] SEC("license") = "GPL";
Annotation
- Immediate include surface: `linux/stddef.h`, `linux/bpf.h`, `linux/in.h`, `sys/socket.h`, `bpf/bpf_helpers.h`, `bpf/bpf_endian.h`, `bpf_sockopt_helpers.h`.
- Detected declarations: `function recvmsg4_prog`.
- 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.