include/linux/netfilter/ipset/ip_set_getport.h

File Facts

System

Linux kernel

Corpus path

include/linux/netfilter/ipset/ip_set_getport.h

Extension

.h

Size

773 bytes

Lines

36

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/skbuff.h
• linux/types.h
• uapi/linux/in.h

Detected Declarations

• function ip_set_get_ip6_port
• function ip_set_proto_with_ports

Annotated Snippet

#ifndef _IP_SET_GETPORT_H
#define _IP_SET_GETPORT_H

#include <linux/skbuff.h>
#include <linux/types.h>
#include <uapi/linux/in.h>

extern bool ip_set_get_ip4_port(const struct sk_buff *skb, bool src,
				__be16 *port, u8 *proto);

#if IS_ENABLED(CONFIG_IP6_NF_IPTABLES)
extern bool ip_set_get_ip6_port(const struct sk_buff *skb, bool src,
				__be16 *port, u8 *proto);
#else
static inline bool ip_set_get_ip6_port(const struct sk_buff *skb, bool src,
				       __be16 *port, u8 *proto)
{
	return false;
}
#endif

static inline bool ip_set_proto_with_ports(u8 proto)
{
	switch (proto) {
	case IPPROTO_TCP:
	case IPPROTO_SCTP:
	case IPPROTO_UDP:
	case IPPROTO_UDPLITE:
		return true;
	}
	return false;
}

#endif /*_IP_SET_GETPORT_H*/

Annotation

• Immediate include surface: `linux/skbuff.h`, `linux/types.h`, `uapi/linux/in.h`.
• Detected declarations: `function ip_set_get_ip6_port`, `function ip_set_proto_with_ports`.
• 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.