net/ipv4/netfilter/nft_reject_ipv4.c

File Facts

System

Linux kernel

Corpus path

net/ipv4/netfilter/nft_reject_ipv4.c

Extension

.c

Size

2019 bytes

Lines

76

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

• linux/kernel.h
• linux/init.h
• linux/module.h
• linux/netlink.h
• linux/netfilter.h
• linux/netfilter/nf_tables.h
• net/netfilter/nf_tables.h
• net/netfilter/ipv4/nf_reject.h
• net/netfilter/nft_reject.h

Detected Declarations

• function Copyright
• function nft_reject_ipv4_module_init
• function nft_reject_ipv4_module_exit
• module init nft_reject_ipv4_module_init

Annotated Snippet

module_init(nft_reject_ipv4_module_init);
module_exit(nft_reject_ipv4_module_exit);

MODULE_LICENSE("GPL");
MODULE_AUTHOR("Patrick McHardy <kaber@trash.net>");
MODULE_ALIAS_NFT_AF_EXPR(AF_INET, "reject");
MODULE_DESCRIPTION("IPv4 packet rejection for nftables");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/init.h`, `linux/module.h`, `linux/netlink.h`, `linux/netfilter.h`, `linux/netfilter/nf_tables.h`, `net/netfilter/nf_tables.h`, `net/netfilter/ipv4/nf_reject.h`.
• Detected declarations: `function Copyright`, `function nft_reject_ipv4_module_init`, `function nft_reject_ipv4_module_exit`, `module init nft_reject_ipv4_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.