include/linux/netfilter_ipv6/ip6_tables.h
Source file repositories/reference/linux-study-clean/include/linux/netfilter_ipv6/ip6_tables.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/netfilter_ipv6/ip6_tables.h- Extension
.h- Size
- 1464 bytes
- Lines
- 55
- Domain
- Core OS
- Bucket
- Core Kernel Interface
- Inferred role
- Core OS: implementation source
- Status
- source implementation candidate
Why This File Exists
Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/if.hlinux/in6.hlinux/init.hlinux/ipv6.hlinux/skbuff.huapi/linux/netfilter_ipv6/ip6_tables.hnet/compat.h
Detected Declarations
struct compat_ip6t_entryfunction compat_ip6t_get_target
Annotated Snippet
struct compat_ip6t_entry {
struct ip6t_ip6 ipv6;
compat_uint_t nfcache;
__u16 target_offset;
__u16 next_offset;
compat_uint_t comefrom;
struct compat_xt_counters counters;
unsigned char elems[];
};
static inline struct xt_entry_target *
compat_ip6t_get_target(struct compat_ip6t_entry *e)
{
return (void *)e + e->target_offset;
}
#endif /* CONFIG_COMPAT */
#endif /* _IP6_TABLES_H */
Annotation
- Immediate include surface: `linux/if.h`, `linux/in6.h`, `linux/init.h`, `linux/ipv6.h`, `linux/skbuff.h`, `uapi/linux/netfilter_ipv6/ip6_tables.h`, `net/compat.h`.
- Detected declarations: `struct compat_ip6t_entry`, `function compat_ip6t_get_target`.
- Atlas domain: Core OS / Core Kernel Interface.
- Implementation status: source 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.