block/bio-integrity-auto.c
Source file repositories/reference/linux-study-clean/block/bio-integrity-auto.c
File Facts
- System
- Linux kernel
- Corpus path
block/bio-integrity-auto.c- Extension
.c- Size
- 3971 bytes
- Lines
- 134
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/blk-integrity.hlinux/t10-pi.hlinux/workqueue.hblk.h
Detected Declarations
struct bio_integrity_datafunction bio_integrity_finishfunction bio_integrity_verify_fnfunction bip_should_checkfunction __bio_integrity_endiofunction bio_integrity_prepfunction blk_flush_integrityfunction blk_integrity_auto_initmodule init blk_integrity_auto_initexport bio_integrity_prep
Annotated Snippet
subsys_initcall(blk_integrity_auto_init);Annotation
- Immediate include surface: `linux/blk-integrity.h`, `linux/t10-pi.h`, `linux/workqueue.h`, `blk.h`.
- Detected declarations: `struct bio_integrity_data`, `function bio_integrity_finish`, `function bio_integrity_verify_fn`, `function bip_should_check`, `function __bio_integrity_endio`, `function bio_integrity_prep`, `function blk_flush_integrity`, `function blk_integrity_auto_init`, `module init blk_integrity_auto_init`, `export bio_integrity_prep`.
- 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.