block/blk-crypto-sysfs.c
Source file repositories/reference/linux-study-clean/block/blk-crypto-sysfs.c
File Facts
- System
- Linux kernel
- Corpus path
block/blk-crypto-sysfs.c- Extension
.c- Size
- 5771 bytes
- Lines
- 209
- Domain
- Representative Device Path
- Bucket
- PCIe NVMe Storage Path
- Inferred role
- Representative Device Path: exported/initcall integration point
- Status
- integration implementation candidate
Why This File Exists
Part of the selected hardware vertical slice: PCI discovery, driver binding, NVMe queues, block requests, DMA, interrupts, and completion.
- Part of the selected hardware vertical slice: PCI discovery, driver binding, NVMe queues, block requests, DMA, interrupts, and completion.
- Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
- Allocates kernel memory; connect allocation flags and lifetime to context constraints.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/blk-crypto-profile.hblk-crypto-internal.h
Detected Declarations
struct blk_crypto_kobjstruct blk_crypto_attrfunction hw_wrapped_keys_showfunction max_dun_bits_showfunction num_keyslots_showfunction raw_keys_showfunction blk_crypto_is_visiblefunction blk_crypto_mode_is_visiblefunction blk_crypto_mode_showfunction blk_crypto_attr_showfunction blk_crypto_releasefunction sysfsfunction blk_crypto_sysfs_unregisterfunction blk_crypto_sysfs_initmodule init blk_crypto_sysfs_init
Annotated Snippet
subsys_initcall(blk_crypto_sysfs_init);Annotation
- Immediate include surface: `linux/blk-crypto-profile.h`, `blk-crypto-internal.h`.
- Detected declarations: `struct blk_crypto_kobj`, `struct blk_crypto_attr`, `function hw_wrapped_keys_show`, `function max_dun_bits_show`, `function num_keyslots_show`, `function raw_keys_show`, `function blk_crypto_is_visible`, `function blk_crypto_mode_is_visible`, `function blk_crypto_mode_show`, `function blk_crypto_attr_show`.
- Atlas domain: Representative Device Path / PCIe NVMe Storage Path.
- Implementation status: integration 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.