include/crypto/gcm.h

File Facts

System

Linux kernel

Corpus path

include/crypto/gcm.h

Extension

.h

Size

1521 bytes

Lines

86

Domain

Repository Root And Misc

Bucket

include

Inferred role

Repository Root And Misc: implementation source

Status

source implementation candidate

Why This File Exists

Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.

• Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/errno.h
• crypto/aes.h
• crypto/gf128hash.h

Detected Declarations

• struct aesgcm_ctx
• function crypto_gcm_check_authsize
• function crypto_rfc4106_check_authsize
• function crypto_ipsec_check_assoclen

Annotated Snippet

struct aesgcm_ctx {
	struct ghash_key	ghash_key;
	struct aes_enckey	aes_key;
	unsigned int		authsize;
};

int aesgcm_expandkey(struct aesgcm_ctx *ctx, const u8 *key,
		     unsigned int keysize, unsigned int authsize);

void aesgcm_encrypt(const struct aesgcm_ctx *ctx, u8 *dst, const u8 *src,
		    int crypt_len, const u8 *assoc, int assoc_len,
		    const u8 iv[GCM_AES_IV_SIZE], u8 *authtag);

bool __must_check aesgcm_decrypt(const struct aesgcm_ctx *ctx, u8 *dst,
				 const u8 *src, int crypt_len, const u8 *assoc,
				 int assoc_len, const u8 iv[GCM_AES_IV_SIZE],
				 const u8 *authtag);

#endif

Annotation

• Immediate include surface: `linux/errno.h`, `crypto/aes.h`, `crypto/gf128hash.h`.
• Detected declarations: `struct aesgcm_ctx`, `function crypto_gcm_check_authsize`, `function crypto_rfc4106_check_authsize`, `function crypto_ipsec_check_assoclen`.
• Atlas domain: Repository Root And Misc / include.
• 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.