drivers/s390/block/dasd_eckd.c
Source file repositories/reference/linux-study-clean/drivers/s390/block/dasd_eckd.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/s390/block/dasd_eckd.c- Extension
.c- Size
- 193234 bytes
- Lines
- 6977
- Domain
- Driver Families
- Bucket
- drivers/s390
- 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.
- Touches user memory; correctness depends on fault-safe copying and privilege boundary handling.
- 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/stddef.hlinux/kernel.hlinux/slab.hlinux/hdreg.hlinux/bio.hlinux/module.hlinux/init.hlinux/seq_file.hlinux/uaccess.hlinux/io.hasm/css_chars.hasm/machine.hasm/debug.hasm/idals.hasm/ebcdic.hasm/cio.hasm/ccwdev.hasm/itcw.hasm/schid.hasm/chpid.hdasd_int.hdasd_eckd.h
Detected Declarations
struct ext_pool_exhaust_work_datastruct pe_handler_work_datastruct check_attention_work_datafunction dasd_eckd_probefunction dasd_eckd_set_onlinefunction ceil_quotfunction recs_per_trackfunction set_ch_tfunction dasd_eckd_track_from_irbfunction set_timestampfunction define_extentfunction locate_record_extfunction prefix_LREfunction prefixfunction locate_recordfunction dasd_eckd_cdl_specialfunction dasd_eckd_cdl_reclenfunction create_uidfunction dasd_eckd_generate_uidfunction dasd_eckd_get_uidfunction dasd_eckd_compare_path_uidfunction dasd_eckd_fill_rcd_cqrfunction read_conf_cbfunction dasd_eckd_read_conf_immediatelyfunction dasd_eckd_read_conf_lpmfunction dasd_eckd_identify_conf_partsfunction dasd_eckd_path_accessfunction dasd_eckd_store_conf_datafunction dasd_eckd_clear_conf_datafunction dasd_eckd_read_fc_securityfunction dasd_eckd_get_uid_stringfunction dasd_eckd_check_cablingfunction dasd_eckd_read_conffunction get_fcx_max_datafunction verify_fcx_max_datafunction rebuild_device_uidfunction dasd_eckd_path_available_actionfunction do_pe_handler_workfunction dasd_eckd_pe_handlerfunction dasd_eckd_reset_pathfunction dasd_eckd_read_featuresfunction dasd_eckd_read_vol_infofunction dasd_eckd_is_esefunction dasd_eckd_ext_pool_idfunction dasd_eckd_space_configuredfunction dasd_eckd_space_allocatedfunction dasd_eckd_logical_capacityfunction dasd_eckd_ext_pool_exhaust_work
Annotated Snippet
module_init(dasd_eckd_init);
module_exit(dasd_eckd_cleanup);
Annotation
- Immediate include surface: `linux/stddef.h`, `linux/kernel.h`, `linux/slab.h`, `linux/hdreg.h`, `linux/bio.h`, `linux/module.h`, `linux/init.h`, `linux/seq_file.h`.
- Detected declarations: `struct ext_pool_exhaust_work_data`, `struct pe_handler_work_data`, `struct check_attention_work_data`, `function dasd_eckd_probe`, `function dasd_eckd_set_online`, `function ceil_quot`, `function recs_per_track`, `function set_ch_t`, `function dasd_eckd_track_from_irb`, `function set_timestamp`.
- Atlas domain: Driver Families / drivers/s390.
- Implementation status: integration implementation candidate.
- This snippet crosses the user/kernel memory boundary; validate fault handling and access checks before translating the pattern.
- 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.