include/linux/netfilter/nf_conntrack_tftp.h
Source file repositories/reference/linux-study-clean/include/linux/netfilter/nf_conntrack_tftp.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/netfilter/nf_conntrack_tftp.h- Extension
.h- Size
- 650 bytes
- Lines
- 30
- 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.hlinux/skbuff.hlinux/types.hnet/netfilter/nf_conntrack_expect.h
Detected Declarations
struct tftphdr
Annotated Snippet
struct tftphdr {
__be16 opcode;
};
#define TFTP_OPCODE_READ 1
#define TFTP_OPCODE_WRITE 2
#define TFTP_OPCODE_DATA 3
#define TFTP_OPCODE_ACK 4
#define TFTP_OPCODE_ERROR 5
typedef unsigned int
nf_nat_tftp_hook_fn(struct sk_buff *skb,
enum ip_conntrack_info ctinfo,
struct nf_conntrack_expect *exp);
extern nf_nat_tftp_hook_fn __rcu *nf_nat_tftp_hook;
#endif /* _NF_CONNTRACK_TFTP_H */
Annotation
- Immediate include surface: `linux/netfilter.h`, `linux/skbuff.h`, `linux/types.h`, `net/netfilter/nf_conntrack_expect.h`.
- Detected declarations: `struct tftphdr`.
- 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.