include/linux/netfilter/nfnetlink_osf.h

File Facts

System

Linux kernel

Corpus path

include/linux/netfilter/nfnetlink_osf.h

Extension

.h

Size

967 bytes

Lines

39

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

• uapi/linux/netfilter/nfnetlink_osf.h

Detected Declarations

• struct nf_osf_finger
• struct nf_osf_data
• enum osf_fmatch_states

Annotated Snippet

struct nf_osf_finger {
	struct rcu_head			rcu_head;
	struct list_head		finger_entry;
	struct nf_osf_user_finger	finger;
};

struct nf_osf_data {
	const char *genre;
	const char *version;
};

bool nf_osf_match(const struct sk_buff *skb, u_int8_t family,
		  int hooknum, struct net_device *in, struct net_device *out,
		  const struct nf_osf_info *info, struct net *net,
		  const struct list_head *nf_osf_fingers);

bool nf_osf_find(const struct sk_buff *skb,
		 const struct list_head *nf_osf_fingers,
		 const int ttl_check, struct nf_osf_data *data);

#endif /* _NFOSF_H */

Annotation

• Immediate include surface: `uapi/linux/netfilter/nfnetlink_osf.h`.
• Detected declarations: `struct nf_osf_finger`, `struct nf_osf_data`, `enum osf_fmatch_states`.
• 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.