include/linux/bpf_crypto.h

File Facts

System

Linux kernel

Corpus path

include/linux/bpf_crypto.h

Extension

.h

Size

865 bytes

Lines

25

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

• No C-style include directives detected by the generator.

Detected Declarations

• struct bpf_crypto_type

Annotated Snippet

struct bpf_crypto_type {
	void *(*alloc_tfm)(const char *algo);
	void (*free_tfm)(void *tfm);
	int (*has_algo)(const char *algo);
	int (*setkey)(void *tfm, const u8 *key, unsigned int keylen);
	int (*setauthsize)(void *tfm, unsigned int authsize);
	int (*encrypt)(void *tfm, const u8 *src, u8 *dst, unsigned int len, u8 *iv);
	int (*decrypt)(void *tfm, const u8 *src, u8 *dst, unsigned int len, u8 *iv);
	unsigned int (*ivsize)(void *tfm);
	unsigned int (*statesize)(void *tfm);
	u32 (*get_flags)(void *tfm);
	struct module *owner;
	char name[14];
};

int bpf_crypto_register_type(const struct bpf_crypto_type *type);
int bpf_crypto_unregister_type(const struct bpf_crypto_type *type);

#endif /* _BPF_CRYPTO_H */

Annotation

• Detected declarations: `struct bpf_crypto_type`.
• 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.