include/crypto/internal/rng.h
Source file repositories/reference/linux-study-clean/include/crypto/internal/rng.h
File Facts
- System
- Linux kernel
- Corpus path
include/crypto/internal/rng.h- Extension
.h- Size
- 1021 bytes
- Lines
- 41
- 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
crypto/algapi.hcrypto/rng.h
Detected Declarations
function crypto_del_default_rngfunction crypto_rng_set_entropy
Annotated Snippet
#ifndef _CRYPTO_INTERNAL_RNG_H
#define _CRYPTO_INTERNAL_RNG_H
#include <crypto/algapi.h>
#include <crypto/rng.h>
int crypto_register_rng(struct rng_alg *alg);
void crypto_unregister_rng(struct rng_alg *alg);
int crypto_register_rngs(struct rng_alg *algs, int count);
void crypto_unregister_rngs(struct rng_alg *algs, int count);
#if defined(CONFIG_CRYPTO_RNG) || defined(CONFIG_CRYPTO_RNG_MODULE)
int crypto_del_default_rng(void);
#else
static inline int crypto_del_default_rng(void)
{
return 0;
}
#endif
static inline void *crypto_rng_ctx(struct crypto_rng *tfm)
{
return crypto_tfm_ctx(&tfm->base);
}
static inline void crypto_rng_set_entropy(struct crypto_rng *tfm,
const u8 *data, unsigned int len)
{
crypto_rng_alg(tfm)->set_ent(tfm, data, len);
}
#endif
Annotation
- Immediate include surface: `crypto/algapi.h`, `crypto/rng.h`.
- Detected declarations: `function crypto_del_default_rng`, `function crypto_rng_set_entropy`.
- 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.