include/linux/netfilter/nf_conntrack_proto_gre.h

File Facts

System

Linux kernel

Corpus path

include/linux/netfilter/nf_conntrack_proto_gre.h

Extension

.h

Size

824 bytes

Lines

32

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

• net/netfilter/nf_conntrack_tuple.h

Detected Declarations

• struct nf_ct_gre
• struct nf_conn
• struct nf_ct_gre_keymap

Annotated Snippet

struct nf_ct_gre {
	unsigned int stream_timeout;
	unsigned int timeout;
};

#include <net/netfilter/nf_conntrack_tuple.h>

struct nf_conn;

/* structure for original <-> reply keymap */
struct nf_ct_gre_keymap {
	struct list_head list;
	struct nf_conntrack_tuple tuple;
	struct rcu_head rcu;
};

/* add tuple->key_reply pairs to keymap */
bool nf_ct_gre_keymap_add(struct nf_conn *ct,
			  const struct nf_conntrack_tuple *orig,
			  const struct nf_conntrack_tuple *repl);

/* delete keymap entries */
void nf_ct_gre_keymap_destroy(struct nf_conn *ct);

bool gre_pkt_to_tuple(const struct sk_buff *skb, unsigned int dataoff,
		      struct net *net, struct nf_conntrack_tuple *tuple);
#endif /* _CONNTRACK_PROTO_GRE_H */

Annotation

• Immediate include surface: `net/netfilter/nf_conntrack_tuple.h`.
• Detected declarations: `struct nf_ct_gre`, `struct nf_conn`, `struct nf_ct_gre_keymap`.
• 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.