include/crypto/blake2s.h
Source file repositories/reference/linux-study-clean/include/crypto/blake2s.h
File Facts
- System
- Linux kernel
- Corpus path
include/crypto/blake2s.h- Extension
.h- Size
- 4506 bytes
- Lines
- 161
- 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/bug.hlinux/kconfig.hlinux/types.hlinux/string.h
Detected Declarations
struct blake2s_ctxenum blake2s_lengthsenum blake2s_ivfunction __blake2s_initfunction blake2s_initfunction blake2s_init_keyfunction blake2s
Annotated Snippet
struct blake2s_ctx {
/* 'h', 't', and 'f' are used in assembly code, so keep them as-is. */
u32 h[8];
u32 t[2];
u32 f[2];
u8 buf[BLAKE2S_BLOCK_SIZE];
unsigned int buflen;
unsigned int outlen;
};
enum blake2s_iv {
BLAKE2S_IV0 = 0x6A09E667UL,
BLAKE2S_IV1 = 0xBB67AE85UL,
BLAKE2S_IV2 = 0x3C6EF372UL,
BLAKE2S_IV3 = 0xA54FF53AUL,
BLAKE2S_IV4 = 0x510E527FUL,
BLAKE2S_IV5 = 0x9B05688CUL,
BLAKE2S_IV6 = 0x1F83D9ABUL,
BLAKE2S_IV7 = 0x5BE0CD19UL,
};
static inline void __blake2s_init(struct blake2s_ctx *ctx, size_t outlen,
const void *key, size_t keylen)
{
ctx->h[0] = BLAKE2S_IV0 ^ (0x01010000 | keylen << 8 | outlen);
ctx->h[1] = BLAKE2S_IV1;
ctx->h[2] = BLAKE2S_IV2;
ctx->h[3] = BLAKE2S_IV3;
ctx->h[4] = BLAKE2S_IV4;
ctx->h[5] = BLAKE2S_IV5;
ctx->h[6] = BLAKE2S_IV6;
ctx->h[7] = BLAKE2S_IV7;
ctx->t[0] = 0;
ctx->t[1] = 0;
ctx->f[0] = 0;
ctx->f[1] = 0;
ctx->buflen = 0;
ctx->outlen = outlen;
if (keylen) {
memcpy(ctx->buf, key, keylen);
memset(&ctx->buf[keylen], 0, BLAKE2S_BLOCK_SIZE - keylen);
ctx->buflen = BLAKE2S_BLOCK_SIZE;
}
}
/**
* blake2s_init() - Initialize a BLAKE2s context for a new message (unkeyed)
* @ctx: the context to initialize
* @outlen: length of output hash value in bytes, at most BLAKE2S_HASH_SIZE
*
* Context: Any context.
*/
static inline void blake2s_init(struct blake2s_ctx *ctx, size_t outlen)
{
__blake2s_init(ctx, outlen, NULL, 0);
}
/**
* blake2s_init_key() - Initialize a BLAKE2s context for a new message (keyed)
* @ctx: the context to initialize
* @outlen: length of output hash value in bytes, at most BLAKE2S_HASH_SIZE
* @key: the key
* @keylen: the key length in bytes, at most BLAKE2S_KEY_SIZE
*
* Context: Any context.
*/
static inline void blake2s_init_key(struct blake2s_ctx *ctx, size_t outlen,
const void *key, size_t keylen)
{
WARN_ON(IS_ENABLED(DEBUG) && (!outlen || outlen > BLAKE2S_HASH_SIZE ||
!key || !keylen || keylen > BLAKE2S_KEY_SIZE));
__blake2s_init(ctx, outlen, key, keylen);
}
/**
* blake2s_update() - Update a BLAKE2s context with message data
* @ctx: the context to update; must have been initialized
* @in: the message data
* @inlen: the data length in bytes
*
* This can be called any number of times.
*
* Context: Any context.
*/
void blake2s_update(struct blake2s_ctx *ctx, const u8 *in, size_t inlen);
/**
* blake2s_final() - Finish computing a BLAKE2s hash
* @ctx: the context to finalize; must have been initialized
Annotation
- Immediate include surface: `linux/bug.h`, `linux/kconfig.h`, `linux/types.h`, `linux/string.h`.
- Detected declarations: `struct blake2s_ctx`, `enum blake2s_lengths`, `enum blake2s_iv`, `function __blake2s_init`, `function blake2s_init`, `function blake2s_init_key`, `function blake2s`.
- 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.