net/netfilter/nft_osf.c

File Facts

System

Linux kernel

Corpus path

net/netfilter/nft_osf.c

Extension

.c

Size

3912 bytes

Lines

169

Domain

Networking Core

Bucket

Sockets, Protocols, Packet Path, And Network Policy

Inferred role

Networking Core: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.

• Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• net/ip.h
• net/tcp.h
• net/netfilter/nf_tables.h
• linux/netfilter/nfnetlink_osf.h

Detected Declarations

• struct nft_osf
• function nft_osf_eval
• function nft_osf_init
• function nft_osf_dump
• function nft_osf_validate
• function nft_osf_module_init
• function nft_osf_module_exit
• module init nft_osf_module_init

Annotated Snippet

module_init(nft_osf_module_init);
module_exit(nft_osf_module_exit);

MODULE_LICENSE("GPL");
MODULE_AUTHOR("Fernando Fernandez <ffmancera@riseup.net>");
MODULE_ALIAS_NFT_EXPR("osf");
MODULE_DESCRIPTION("nftables passive OS fingerprint support");

Annotation

• Immediate include surface: `net/ip.h`, `net/tcp.h`, `net/netfilter/nf_tables.h`, `linux/netfilter/nfnetlink_osf.h`.
• Detected declarations: `struct nft_osf`, `function nft_osf_eval`, `function nft_osf_init`, `function nft_osf_dump`, `function nft_osf_validate`, `function nft_osf_module_init`, `function nft_osf_module_exit`, `module init nft_osf_module_init`.
• Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
• Implementation status: integration 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.