drivers/scsi/scsi.c

File Facts

System

Linux kernel

Corpus path

drivers/scsi/scsi.c

Extension

.c

Size

29538 bytes

Lines

1079

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• 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/module.h
• linux/moduleparam.h
• linux/kernel.h
• linux/timer.h
• linux/string.h
• linux/slab.h
• linux/blkdev.h
• linux/delay.h
• linux/init.h
• linux/completion.h
• linux/unistd.h
• linux/spinlock.h
• linux/kmod.h
• linux/interrupt.h
• linux/notifier.h
• linux/cpu.h
• linux/mutex.h
• linux/unaligned.h
• scsi/scsi.h
• scsi/scsi_cmnd.h
• scsi/scsi_dbg.h
• scsi/scsi_device.h
• scsi/scsi_driver.h
• scsi/scsi_eh.h
• scsi/scsi_host.h
• scsi/scsi_tcq.h
• scsi_priv.h
• scsi_logging.h
• trace/events/scsi.h

Detected Declarations

• enum scsi_vpd_parameters
• function scsi_log_send
• function scsi_log_completion
• function scsi_finish_command
• function scsi_device_max_queue_depth
• function scsi_change_queue_depth
• function scsi_track_queue_full
• function scsi_vpd_inquiry
• function scsi_get_vpd_size
• function document
• function scsi_update_vpd_page
• function scsi_attach_vpd
• function scsi_report_opcode
• function scsi_cdl_check_cmd
• function scsi_cdl_check
• function scsi_cdl_enable
• function scsi_device_get
• function scsi_device_put
• function starget_for_each_device
• function shost_for_each_device
• function __starget_for_each_device
• function __shost_for_each_device
• function list_for_each_entry
• function list_for_each_entry
• function init_scsi
• function exit_scsi
• module init init_scsi
• export scsi_logging_level
• export scsi_change_queue_depth
• export scsi_track_queue_full
• export scsi_get_vpd_page
• export scsi_report_opcode
• export scsi_device_get
• export scsi_device_put
• export __scsi_iterate_devices
• export starget_for_each_device
• export __starget_for_each_device
• export __scsi_device_lookup_by_target
• export scsi_device_lookup_by_target
• export __scsi_device_lookup
• export scsi_device_lookup

Annotated Snippet

subsys_initcall(init_scsi);
module_exit(exit_scsi);

Annotation

• Immediate include surface: `linux/module.h`, `linux/moduleparam.h`, `linux/kernel.h`, `linux/timer.h`, `linux/string.h`, `linux/slab.h`, `linux/blkdev.h`, `linux/delay.h`.
• Detected declarations: `enum scsi_vpd_parameters`, `function scsi_log_send`, `function scsi_log_completion`, `function scsi_finish_command`, `function scsi_device_max_queue_depth`, `function scsi_change_queue_depth`, `function scsi_track_queue_full`, `function scsi_vpd_inquiry`, `function scsi_get_vpd_size`, `function document`.
• Atlas domain: Driver Families / drivers/scsi.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.