net/netfilter/xt_time.c

File Facts

System

Linux kernel

Corpus path

net/netfilter/xt_time.c

Extension

.c

Size

8560 bytes

Lines

296

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/ktime.h
• linux/module.h
• linux/rtc.h
• linux/skbuff.h
• linux/types.h
• linux/netfilter/x_tables.h
• linux/netfilter/xt_time.h

Detected Declarations

• struct xtm
• function a
• function localtime_2
• function localtime_3
• function month
• function time_mt
• function time_mt_check
• function time_mt_init
• function time_mt_exit
• module init time_mt_init

Annotated Snippet

module_init(time_mt_init);
module_exit(time_mt_exit);
MODULE_AUTHOR("Jan Engelhardt <jengelh@medozas.de>");
MODULE_DESCRIPTION("Xtables: time-based matching");
MODULE_LICENSE("GPL");
MODULE_ALIAS("ipt_time");
MODULE_ALIAS("ip6t_time");

Annotation

• Immediate include surface: `linux/ktime.h`, `linux/module.h`, `linux/rtc.h`, `linux/skbuff.h`, `linux/types.h`, `linux/netfilter/x_tables.h`, `linux/netfilter/xt_time.h`.
• Detected declarations: `struct xtm`, `function a`, `function localtime_2`, `function localtime_3`, `function month`, `function time_mt`, `function time_mt_check`, `function time_mt_init`, `function time_mt_exit`, `module init time_mt_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.