net/bridge/netfilter/ebt_ip6.c

File Facts

System

Linux kernel

Corpus path

net/bridge/netfilter/ebt_ip6.c

Extension

.c

Size

4572 bytes

Lines

165

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/ipv6.h
• net/ipv6.h
• linux/in.h
• linux/module.h
• net/dsfield.h
• linux/netfilter/x_tables.h
• linux/netfilter_bridge/ebtables.h
• linux/netfilter_bridge/ebt_ip6.h

Detected Declarations

• function ebt_ip6_mt
• function ebt_ip6_mt_check
• function ebt_ip6_init
• function ebt_ip6_fini
• module init ebt_ip6_init

Annotated Snippet

module_init(ebt_ip6_init);
module_exit(ebt_ip6_fini);
MODULE_DESCRIPTION("Ebtables: IPv6 protocol packet match");
MODULE_AUTHOR("Kuo-Lang Tseng <kuo-lang.tseng@intel.com>");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/ipv6.h`, `net/ipv6.h`, `linux/in.h`, `linux/module.h`, `net/dsfield.h`, `linux/netfilter/x_tables.h`, `linux/netfilter_bridge/ebtables.h`, `linux/netfilter_bridge/ebt_ip6.h`.
• Detected declarations: `function ebt_ip6_mt`, `function ebt_ip6_mt_check`, `function ebt_ip6_init`, `function ebt_ip6_fini`, `module init ebt_ip6_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.