drivers/md/dm-clone-target.c

File Facts

System

Linux kernel

Corpus path

drivers/md/dm-clone-target.c

Extension

.c

Size

54943 bytes

Lines

2209

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.
• 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/mm.h
• linux/bio.h
• linux/err.h
• linux/hash.h
• linux/list.h
• linux/log2.h
• linux/init.h
• linux/slab.h
• linux/wait.h
• linux/dm-io.h
• linux/mutex.h
• linux/atomic.h
• linux/bitops.h
• linux/blkdev.h
• linux/kdev_t.h
• linux/kernel.h
• linux/module.h
• linux/jiffies.h
• linux/mempool.h
• linux/spinlock.h
• linux/blk_types.h
• linux/dm-kcopyd.h
• linux/workqueue.h
• linux/backing-dev.h
• linux/device-mapper.h
• dm.h
• dm-clone-metadata.h

Detected Declarations

• struct hash_table_bucket
• struct clone
• struct dm_clone_region_hydration
• struct hash_table_bucket
• struct batch_info
• enum clone_metadata_mode
• function get_clone_mode
• function __set_clone_mode
• function __abort_transaction
• function __reload_in_core_bitset
• function __metadata_operation_failed
• function wakeup_hydration_waiters
• function wake_worker
• function remap_to_source
• function remap_to_dest
• function bio_triggers_commit
• function region_to_sector
• function bio_to_region
• function bio_region_range
• function is_overwrite_bio
• function fail_bios
• function submit_bios
• function issue_bio
• function remap_and_issue
• function issue_deferred_bios
• function complete_overwrite_bio
• function complete_overwrite_bio
• function trim_bio
• function complete_discard_bio
• function process_discard_bio
• function hash_table_init
• function hash_table_exit
• function hlist_for_each_entry
• function __insert_region_hydration
• function __find_or_insert_region_hydration
• function free_hydration
• function hydration_init
• function hydration_update_metadata
• function hydration_complete
• function hydration_kcopyd_callback
• function hydration_copy
• function overwrite_endio
• function hydration_overwrite
• function hydrate_bio_region
• function __batch_hydration
• function __start_next_hydration
• function do_hydration
• function test_bit

Annotated Snippet

module_init(dm_clone_init);
module_exit(dm_clone_exit);

MODULE_DESCRIPTION(DM_NAME " clone target");
MODULE_AUTHOR("Nikos Tsironis <ntsironis@arrikto.com>");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/mm.h`, `linux/bio.h`, `linux/err.h`, `linux/hash.h`, `linux/list.h`, `linux/log2.h`, `linux/init.h`, `linux/slab.h`.
• Detected declarations: `struct hash_table_bucket`, `struct clone`, `struct dm_clone_region_hydration`, `struct hash_table_bucket`, `struct batch_info`, `enum clone_metadata_mode`, `function get_clone_mode`, `function __set_clone_mode`, `function __abort_transaction`, `function __reload_in_core_bitset`.
• 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.