drivers/scsi/raid_class.c

File Facts

System

Linux kernel

Corpus path

drivers/scsi/raid_class.c

Extension

.c

Size

6653 bytes

Lines

268

Domain

Driver Families

Bucket

drivers/scsi

Inferred role

Driver Families: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• 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/init.h
• linux/module.h
• linux/list.h
• linux/slab.h
• linux/string.h
• linux/raid_class.h
• scsi/scsi_device.h
• scsi/scsi_host.h

Detected Declarations

• struct raid_internal
• struct raid_component
• function raid_match
• function raid_setup
• function raid_remove
• function raid_class_attach
• function raid_class_release
• function raid_init
• function raid_exit
• module init raid_init
• export raid_class_attach
• export raid_class_release

Annotated Snippet

module_init(raid_init);
module_exit(raid_exit);

Annotation

• Immediate include surface: `linux/init.h`, `linux/module.h`, `linux/list.h`, `linux/slab.h`, `linux/string.h`, `linux/raid_class.h`, `scsi/scsi_device.h`, `scsi/scsi_host.h`.
• Detected declarations: `struct raid_internal`, `struct raid_component`, `function raid_match`, `function raid_setup`, `function raid_remove`, `function raid_class_attach`, `function raid_class_release`, `function raid_init`, `function raid_exit`, `module init raid_init`.
• Atlas domain: Driver Families / drivers/scsi.
• 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.