net/bridge/netfilter/ebtable_broute.c

File Facts

System

Linux kernel

Corpus path

net/bridge/netfilter/ebtable_broute.c

Extension

.c

Size

3337 bytes

Lines

137

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/netfilter_bridge/ebtables.h
• linux/module.h
• linux/if_bridge.h
• ../br_private.h

Detected Declarations

• function ebt_broute
• function broute_table_init
• function broute_net_pre_exit
• function broute_net_exit
• function ebtable_broute_init
• function ebtable_broute_fini
• module init ebtable_broute_init

Annotated Snippet

module_init(ebtable_broute_init);
module_exit(ebtable_broute_fini);
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("Force packets to be routed instead of bridged");

Annotation

• Immediate include surface: `linux/netfilter_bridge/ebtables.h`, `linux/module.h`, `linux/if_bridge.h`, `../br_private.h`.
• Detected declarations: `function ebt_broute`, `function broute_table_init`, `function broute_net_pre_exit`, `function broute_net_exit`, `function ebtable_broute_init`, `function ebtable_broute_fini`, `module init ebtable_broute_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.