include/crypto/xts.h
Source file repositories/reference/linux-study-clean/include/crypto/xts.h
File Facts
- System
- Linux kernel
- Corpus path
include/crypto/xts.h- Extension
.h- Size
- 978 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/b128ops.hcrypto/internal/skcipher.hlinux/fips.h
Detected Declarations
function xts_verify_key
Annotated Snippet
#ifndef _CRYPTO_XTS_H
#define _CRYPTO_XTS_H
#include <crypto/b128ops.h>
#include <crypto/internal/skcipher.h>
#include <linux/fips.h>
#define XTS_BLOCK_SIZE 16
static inline int xts_verify_key(struct crypto_skcipher *tfm,
const u8 *key, unsigned int keylen)
{
/*
* key consists of keys of equal size concatenated, therefore
* the length must be even.
*/
if (keylen % 2)
return -EINVAL;
/*
* In FIPS mode only a combined key length of either 256 or
* 512 bits is allowed, c.f. FIPS 140-3 IG C.I.
*/
if (fips_enabled && keylen != 32 && keylen != 64)
return -EINVAL;
/*
* Ensure that the AES and tweak key are not identical when
* in FIPS mode or the FORBID_WEAK_KEYS flag is set.
*/
if ((fips_enabled || (crypto_skcipher_get_flags(tfm) &
CRYPTO_TFM_REQ_FORBID_WEAK_KEYS)) &&
!crypto_memneq(key, key + (keylen / 2), keylen / 2))
return -EINVAL;
return 0;
}
#endif /* _CRYPTO_XTS_H */
Annotation
- Immediate include surface: `crypto/b128ops.h`, `crypto/internal/skcipher.h`, `linux/fips.h`.
- Detected declarations: `function xts_verify_key`.
- 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.