net/mac80211/aead_api.h

File Facts

System

Linux kernel

Corpus path

net/mac80211/aead_api.h

Extension

.h

Size

569 bytes

Lines

24

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

• crypto/aead.h
• linux/crypto.h

Detected Declarations

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

Annotated Snippet

#ifndef _AEAD_API_H
#define _AEAD_API_H

#include <crypto/aead.h>
#include <linux/crypto.h>

struct crypto_aead *
aead_key_setup_encrypt(const char *alg, const u8 key[],
		       size_t key_len, size_t mic_len);

int aead_encrypt(struct crypto_aead *tfm, u8 *b_0, u8 *aad,
		 size_t aad_len, u8 *data,
		 size_t data_len, u8 *mic);

int aead_decrypt(struct crypto_aead *tfm, u8 *b_0, u8 *aad,
		 size_t aad_len, u8 *data,
		 size_t data_len, u8 *mic);

void aead_key_free(struct crypto_aead *tfm);

#endif /* _AEAD_API_H */

Annotation

• Immediate include surface: `crypto/aead.h`, `linux/crypto.h`.
• 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.