include/net/calipso.h

Source file repositories/reference/linux-study-clean/include/net/calipso.h

File Facts

System: Linux kernel
Corpus path: include/net/calipso.h
Extension: .h
Size: 1592 bytes
Lines: 78
Domain: Networking Core
Bucket: Sockets, Protocols, Packet Path, And Network Policy
Inferred role: Networking Core: implementation source
Status: source 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.
Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

linux/types.h
linux/rcupdate.h
linux/list.h
linux/net.h
linux/skbuff.h
net/netlabel.h
net/request_sock.h
linux/refcount.h
linux/unaligned.h

Detected Declarations

struct calipso_doi
function calipso_init
function calipso_exit

Annotated Snippet

struct calipso_doi {
	u32 doi;
	u32 type;

	refcount_t refcount;
	struct list_head list;
	struct rcu_head rcu;
};

/*
 * Sysctl Variables
 */
extern int calipso_cache_enabled;
extern int calipso_cache_bucketsize;

#ifdef CONFIG_NETLABEL
int __init calipso_init(void);
void calipso_exit(void);
bool calipso_validate(const struct sk_buff *skb, const unsigned char *option);
#else
static inline int __init calipso_init(void)
{
	return 0;
}

static inline void calipso_exit(void)
{
}
static inline bool calipso_validate(const struct sk_buff *skb,
				    const unsigned char *option)
{
	return true;
}
#endif /* CONFIG_NETLABEL */

#endif /* _CALIPSO_H */

Annotation

Immediate include surface: `linux/types.h`, `linux/rcupdate.h`, `linux/list.h`, `linux/net.h`, `linux/skbuff.h`, `net/netlabel.h`, `net/request_sock.h`, `linux/refcount.h`.
Detected declarations: `struct calipso_doi`, `function calipso_init`, `function calipso_exit`.
Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
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.