samples/bpf/tcp_tos_reflect_kern.c
Source file repositories/reference/linux-study-clean/samples/bpf/tcp_tos_reflect_kern.c
File Facts
- System
- Linux kernel
- Corpus path
samples/bpf/tcp_tos_reflect_kern.c- Extension
.c- Size
- 1833 bytes
- Lines
- 81
- Domain
- Support Tooling And Documentation
- Bucket
- samples
- 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
uapi/linux/bpf.huapi/linux/tcp.huapi/linux/if_ether.huapi/linux/if_packet.huapi/linux/ip.huapi/linux/ipv6.huapi/linux/in.hlinux/socket.hbpf/bpf_helpers.hbpf/bpf_endian.h
Detected Declarations
function Copyright
Annotated Snippet
if (!rv) {
if (skops->family == AF_INET) {
hdr = (struct iphdr *) header;
tos = hdr->tos;
if (tos != 0)
bpf_setsockopt(skops, SOL_IP, IP_TOS,
&tos, sizeof(tos));
} else {
hdr6 = (struct ipv6hdr *) header;
tos = ((hdr6->priority) << 4 |
(hdr6->flow_lbl[0]) >> 4);
if (tos)
bpf_setsockopt(skops, SOL_IPV6,
IPV6_TCLASS,
&tos, sizeof(tos));
}
rv = 0;
}
break;
default:
rv = -1;
}
#ifdef DEBUG
bpf_printk("Returning %d\n", rv);
#endif
skops->reply = rv;
return 1;
}
char _license[] SEC("license") = "GPL";
Annotation
- Immediate include surface: `uapi/linux/bpf.h`, `uapi/linux/tcp.h`, `uapi/linux/if_ether.h`, `uapi/linux/if_packet.h`, `uapi/linux/ip.h`, `uapi/linux/ipv6.h`, `uapi/linux/in.h`, `linux/socket.h`.
- Detected declarations: `function Copyright`.
- Atlas domain: Support Tooling And Documentation / samples.
- 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.