net/sched/act_ife.c

File Facts

System

Linux kernel

Corpus path

net/sched/act_ife.c

Extension

.c

Size

20585 bytes

Lines

928

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/types.h
• linux/kernel.h
• linux/string.h
• linux/errno.h
• linux/skbuff.h
• linux/rtnetlink.h
• linux/module.h
• linux/init.h
• net/net_namespace.h
• net/netlink.h
• net/pkt_sched.h
• net/pkt_cls.h
• uapi/linux/tc_act/tc_ife.h
• net/tc_act/tc_ife.h
• linux/etherdevice.h
• net/ife.h
• net/tc_wrapper.h

Detected Declarations

• function ife_encode_meta_u16
• function ife_get_meta_u32
• function ife_check_meta_u32
• function ife_check_meta_u16
• function ife_encode_meta_u32
• function ife_get_meta_u16
• function ife_alloc_meta_u32
• function ife_alloc_meta_u16
• function ife_release_meta_gen
• function ife_validate_meta_u32
• function ife_validate_meta_u16
• function register_ife_op
• function list_for_each_entry
• function unregister_ife_op
• function ife_validate_metatype
• function load_metaops_and_vet
• function __add_metainfo
• function add_metainfo_and_get_ops
• function add_metainfo
• function use_all_metadata
• function dump_metalist
• function list_for_each_entry
• function __tcf_ife_cleanup
• function list_for_each_entry_safe
• function tcf_ife_cleanup_params
• function tcf_ife_cleanup
• function load_metalist
• function populate_metalist
• function tcf_ife_init
• function tcf_ife_dump
• function find_decode_metaid
• function tcf_ife_decode
• function ife_get_sz
• function list_for_each_entry_rcu
• function tcf_ife_encode
• function tcf_ife_act
• function ife_init_net
• function ife_exit_net
• function ife_init_module
• function ife_cleanup_module
• module init ife_init_module
• export ife_encode_meta_u16
• export ife_get_meta_u32
• export ife_check_meta_u32
• export ife_check_meta_u16
• export ife_encode_meta_u32
• export ife_get_meta_u16
• export ife_alloc_meta_u32

Annotated Snippet

module_init(ife_init_module);
module_exit(ife_cleanup_module);

MODULE_AUTHOR("Jamal Hadi Salim(2015)");
MODULE_DESCRIPTION("Inter-FE LFB action");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/types.h`, `linux/kernel.h`, `linux/string.h`, `linux/errno.h`, `linux/skbuff.h`, `linux/rtnetlink.h`, `linux/module.h`, `linux/init.h`.
• Detected declarations: `function ife_encode_meta_u16`, `function ife_get_meta_u32`, `function ife_check_meta_u32`, `function ife_check_meta_u16`, `function ife_encode_meta_u32`, `function ife_get_meta_u16`, `function ife_alloc_meta_u32`, `function ife_alloc_meta_u16`, `function ife_release_meta_gen`, `function ife_validate_meta_u32`.
• 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.