drivers/md/raid1.c

File Facts

System

Linux kernel

Corpus path

drivers/md/raid1.c

Extension

.c

Size

95735 bytes

Lines

3523

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/slab.h
• linux/delay.h
• linux/blkdev.h
• linux/module.h
• linux/seq_file.h
• linux/ratelimit.h
• linux/interval_tree_generic.h
• trace/events/block.h
• md.h
• raid1.h
• md-bitmap.h
• md-cluster.h
• raid1-10.c

Detected Declarations

• struct read_balance_ctl
• function check_and_add_serial
• function wait_for_serialization
• function remove_serial
• function r1buf_pool_alloc
• function r1buf_pool_free
• function put_all_bios
• function free_r1bio
• function put_buf
• function reschedule_retry
• function raid_end_bio_io
• function raid_end_bio_io
• function update_head_pos
• function find_bio_disk
• function raid1_end_read_request
• function test_bit
• function close_write
• function r1_bio_write_done
• function raid1_end_write_request
• function align_to_barrier_unit_end
• function update_read_sectors
• function choose_first_rdev
• function rdev_in_recovery
• function choose_bb_rdev
• function choose_slow_rdev
• function is_sequential
• function should_choose_next
• function rdev_readable
• function choose_best_rdev
• function read_balance
• function wake_up_barrier
• function flush_bio_list
• function flush_pending_writes
• function raise_barrier
• function lower_barrier
• function _wait_barrier
• function wait_read_barrier
• function wait_barrier
• function _allow_barrier
• function allow_barrier
• function get_unqueued_pending
• function freeze_array
• function unfreeze_array
• function alloc_behind_master_bio
• function raid1_unplug
• function init_r1bio
• function alloc_r1bio
• function raid1_read_request

Annotated Snippet

module_init(raid1_init);
module_exit(raid1_exit);
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("RAID1 (mirroring) personality for MD");
MODULE_ALIAS("md-personality-3"); /* RAID1 */
MODULE_ALIAS("md-raid1");
MODULE_ALIAS("md-level-1");

Annotation

• Immediate include surface: `linux/slab.h`, `linux/delay.h`, `linux/blkdev.h`, `linux/module.h`, `linux/seq_file.h`, `linux/ratelimit.h`, `linux/interval_tree_generic.h`, `trace/events/block.h`.
• Detected declarations: `struct read_balance_ctl`, `function check_and_add_serial`, `function wait_for_serialization`, `function remove_serial`, `function r1buf_pool_alloc`, `function r1buf_pool_free`, `function put_all_bios`, `function free_r1bio`, `function put_buf`, `function reschedule_retry`.
• 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.