drivers/target/tcm_remote/tcm_remote.c

File Facts

System

Linux kernel

Corpus path

drivers/target/tcm_remote/tcm_remote.c

Extension

.c

Size

7115 bytes

Lines

269

Domain

Driver Families

Bucket

drivers/target

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/module.h
• linux/moduleparam.h
• linux/init.h
• linux/slab.h
• linux/types.h
• linux/configfs.h
• scsi/scsi.h
• scsi/scsi_tcq.h
• scsi/scsi_host.h
• scsi/scsi_device.h
• scsi/scsi_cmnd.h
• target/target_core_base.h
• target/target_core_fabric.h
• tcm_remote.h

Detected Declarations

• function tcm_remote_get_tag
• function tcm_remote_dummy_cmd_fn
• function tcm_remote_dummy_cmd_void_fn
• function tcm_remote_port_link
• function tcm_remote_port_unlink
• function tcm_remote_drop_tpg
• function tcm_remote_drop_wwn
• function tcm_remote_wwn_version_show
• function tcm_remote_fabric_init
• function tcm_remote_fabric_exit
• module init tcm_remote_fabric_init

Annotated Snippet

module_init(tcm_remote_fabric_init);
module_exit(tcm_remote_fabric_exit);

Annotation

• Immediate include surface: `linux/module.h`, `linux/moduleparam.h`, `linux/init.h`, `linux/slab.h`, `linux/types.h`, `linux/configfs.h`, `scsi/scsi.h`, `scsi/scsi_tcq.h`.
• Detected declarations: `function tcm_remote_get_tag`, `function tcm_remote_dummy_cmd_fn`, `function tcm_remote_dummy_cmd_void_fn`, `function tcm_remote_port_link`, `function tcm_remote_port_unlink`, `function tcm_remote_drop_tpg`, `function tcm_remote_drop_wwn`, `function tcm_remote_wwn_version_show`, `function tcm_remote_fabric_init`, `function tcm_remote_fabric_exit`.
• Atlas domain: Driver Families / drivers/target.
• 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.