drivers/md/dm-vdo/dm-vdo-target.c

File Facts

System

Linux kernel

Corpus path

drivers/md/dm-vdo/dm-vdo-target.c

Extension

.c

Size

92862 bytes

Lines

3062

Domain

Driver Families

Bucket

drivers/md

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/atomic.h
• linux/bitops.h
• linux/completion.h
• linux/delay.h
• linux/device-mapper.h
• linux/err.h
• linux/log2.h
• linux/module.h
• linux/mutex.h
• linux/spinlock.h
• admin-state.h
• block-map.h
• completion.h
• constants.h
• data-vio.h
• dedupe.h
• dump.h
• encodings.h
• errors.h
• flush.h
• io-submitter.h
• logger.h
• memory-alloc.h
• message-stats.h
• recovery-journal.h
• repair.h
• slab-depot.h
• status-codes.h
• string-utils.h
• thread-device.h
• thread-registry.h
• thread-utils.h

Detected Declarations

• struct instance_tracker
• enum admin_phases
• function free_device_config
• function get_version_number
• function free_string_array
• function split_string
• function join_strings
• function parse_bool
• function parse_memory
• function parse_slab_size
• function process_one_thread_config_spec
• function parse_one_thread_config_spec
• function parse_thread_config_string
• function process_one_key_value_pair
• function parse_one_key_value_pair
• function parse_key_value_pairs
• function parse_optional_arguments
• function handle_parse_error
• function parse_device_config
• function vdo_map_bio
• function vdo_io_hints
• function vdo_iterate_devices
• function vdo_status
• function get_underlying_device_block_count
• function process_vdo_message_locked
• function process_vdo_message
• function vdo_message
• function configure_target_capabilities
• function vdo_uses_device
• function get_thread_id_for_phase
• function advance_phase
• function operation
• function assert_admin_phase_thread
• function finish_operation_callback
• function decode_from_super_block
• function decode_vdo
• function pre_load_callback
• function release_instance
• function set_device_config
• function vdo_initialize
• function vdo_is_named
• function get_bit_array_size
• function grow_bit_array
• function allocate_instance
• function construct_new_vdo_registered
• function construct_new_vdo
• function check_may_grow_physical
• function get_partition_size

Annotated Snippet

module_init(vdo_init);
module_exit(vdo_exit);

module_param_named(log_level, vdo_log_level, uint, 0644);
MODULE_PARM_DESC(log_level, "Log level for log messages");

MODULE_DESCRIPTION(DM_NAME " target for transparent deduplication");
MODULE_AUTHOR("Red Hat, Inc.");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/atomic.h`, `linux/bitops.h`, `linux/completion.h`, `linux/delay.h`, `linux/device-mapper.h`, `linux/err.h`, `linux/log2.h`, `linux/module.h`.
• Detected declarations: `struct instance_tracker`, `enum admin_phases`, `function free_device_config`, `function get_version_number`, `function free_string_array`, `function split_string`, `function join_strings`, `function parse_bool`, `function parse_memory`, `function parse_slab_size`.
• Atlas domain: Driver Families / drivers/md.
• 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.