net/netfilter/xt_SECMARK.c
Source file repositories/reference/linux-study-clean/net/netfilter/xt_SECMARK.c
File Facts
- System
- Linux kernel
- Corpus path
net/netfilter/xt_SECMARK.c- Extension
.c- Size
- 4954 bytes
- Lines
- 215
- 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/module.hlinux/security.hlinux/skbuff.hlinux/netfilter/x_tables.hlinux/netfilter/xt_SECMARK.h
Detected Declarations
function secmark_tgfunction checkentry_lsmfunction secmark_tg_checkfunction secmark_tg_destroyfunction secmark_tg_check_v0function secmark_tg_v0function secmark_tg_check_v1function secmark_tg_v1function secmark_tg_initfunction secmark_tg_exitmodule init secmark_tg_init
Annotated Snippet
module_init(secmark_tg_init);
module_exit(secmark_tg_exit);Annotation
- Immediate include surface: `linux/module.h`, `linux/security.h`, `linux/skbuff.h`, `linux/netfilter/x_tables.h`, `linux/netfilter/xt_SECMARK.h`.
- Detected declarations: `function secmark_tg`, `function checkentry_lsm`, `function secmark_tg_check`, `function secmark_tg_destroy`, `function secmark_tg_check_v0`, `function secmark_tg_v0`, `function secmark_tg_check_v1`, `function secmark_tg_v1`, `function secmark_tg_init`, `function secmark_tg_exit`.
- 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.