include/linux/netfilter/nf_conntrack_amanda.h

File Facts

System

Linux kernel

Corpus path

include/linux/netfilter/nf_conntrack_amanda.h

Extension

.h

Size

558 bytes

Lines

20

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/netfilter.h
• linux/skbuff.h
• net/netfilter/nf_conntrack_expect.h

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef _NF_CONNTRACK_AMANDA_H
#define _NF_CONNTRACK_AMANDA_H
/* AMANDA tracking. */

#include <linux/netfilter.h>
#include <linux/skbuff.h>
#include <net/netfilter/nf_conntrack_expect.h>

typedef unsigned int
nf_nat_amanda_hook_fn(struct sk_buff *skb,
		      enum ip_conntrack_info ctinfo,
		      unsigned int protoff,
		      unsigned int matchoff,
		      unsigned int matchlen,
		      struct nf_conntrack_expect *exp);

extern nf_nat_amanda_hook_fn __rcu *nf_nat_amanda_hook;
#endif /* _NF_CONNTRACK_AMANDA_H */

Annotation

• Immediate include surface: `linux/netfilter.h`, `linux/skbuff.h`, `net/netfilter/nf_conntrack_expect.h`.
• 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.