net/netfilter/nft_compat.c

File Facts

System

Linux kernel

Corpus path

net/netfilter/nft_compat.c

Extension

.c

Size

24587 bytes

Lines

1009

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• 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/nfnetlink.h
• linux/netfilter/nf_tables.h
• linux/netfilter/nf_tables_compat.h
• linux/netfilter/x_tables.h
• linux/netfilter_ipv4/ip_tables.h
• linux/netfilter_ipv6/ip6_tables.h
• linux/netfilter_bridge/ebtables.h
• linux/netfilter_arp/arp_tables.h
• net/netfilter/nf_tables.h
• net/netfilter/nf_log.h

Detected Declarations

• struct nft_xt_match_priv
• function nft_compat_chain_validate_dependency
• function nft_compat_set_par
• function nft_target_eval_xt
• function nft_target_eval_bridge
• function nft_target_set_tgchk_param
• function target_compat_from_user
• function nft_parse_compat
• function nft_compat_wait_for_destructors
• function nft_target_init
• function __nft_mt_tg_destroy
• function nft_target_destroy
• function nft_extension_dump_info
• function nft_target_dump
• function nft_target_validate
• function __nft_match_eval
• function nft_match_large_eval
• function nft_match_eval
• function nft_match_set_mtchk_param
• function match_compat_from_user
• function __nft_match_init
• function nft_match_init
• function nft_match_large_init
• function __nft_match_destroy
• function nft_match_destroy
• function nft_match_large_destroy
• function __nft_match_dump
• function nft_match_dump
• function nft_match_large_dump
• function nft_match_validate
• function nfnl_compat_fill_info
• function nfnl_compat_get_rcu
• function NFNL_MSG_TYPE
• function nft_match_select_ops
• function nft_match_release_ops
• function nft_target_select_ops
• function nft_target_release_ops
• function nft_compat_module_init
• function nft_compat_module_exit
• module init nft_compat_module_init

Annotated Snippet

module_init(nft_compat_module_init);
module_exit(nft_compat_module_exit);

MODULE_LICENSE("GPL");
MODULE_AUTHOR("Pablo Neira Ayuso <pablo@netfilter.org>");
MODULE_ALIAS_NFT_EXPR("match");
MODULE_ALIAS_NFT_EXPR("target");
MODULE_DESCRIPTION("x_tables over nftables support");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/init.h`, `linux/module.h`, `linux/netlink.h`, `linux/netfilter.h`, `linux/netfilter/nfnetlink.h`, `linux/netfilter/nf_tables.h`, `linux/netfilter/nf_tables_compat.h`.
• Detected declarations: `struct nft_xt_match_priv`, `function nft_compat_chain_validate_dependency`, `function nft_compat_set_par`, `function nft_target_eval_xt`, `function nft_target_eval_bridge`, `function nft_target_set_tgchk_param`, `function target_compat_from_user`, `function nft_parse_compat`, `function nft_compat_wait_for_destructors`, `function nft_target_init`.
• Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.