drivers/md/raid5.c

File Facts

System

Linux kernel

Corpus path

drivers/md/raid5.c

Extension

.c

Size

261809 bytes

Lines

9177

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.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• 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/blkdev.h
• linux/kthread.h
• linux/raid/pq.h
• linux/async_tx.h
• linux/module.h
• linux/async.h
• linux/seq_file.h
• linux/cpu.h
• linux/slab.h
• linux/ratelimit.h
• linux/nodemask.h
• trace/events/block.h
• linux/list_sort.h
• md.h
• raid5.h
• raid0.h
• md-bitmap.h
• raid5-log.h

Detected Declarations

• struct stripe_request_ctx
• struct raid5_plug_cb
• enum stripe_result
• enum reshape_loc
• function stripe_hash_locks_hash
• function lock_device_hash_lock
• function unlock_device_hash_lock
• function lock_all_device_hash_locks_irq
• function unlock_all_device_hash_locks_irq
• function raid6_d0
• function raid6_next_disk
• function raid6_idx_to_slot
• function stripe_operations_active
• function stripe_is_lowprio
• function raid5_wakeup_stripe_thread
• function do_release_stripe
• function __release_stripe
• function release_inactive_stripe_list
• function release_stripe_list
• function raid5_release_stripe
• function remove_hash
• function insert_hash
• function free_stripe_pages
• function alloc_stripe_pages
• function init_stripe_shared_pages
• function shrink_buffers
• function grow_buffers
• function init_stripe
• function raid5_run
• function has_failed
• function is_inactive_blocked
• function is_full_stripe_write
• function lock_two_stripes
• function unlock_two_stripes
• function stripe_can_batch
• function stripe_add_to_batch_list
• function use_new_offset
• function dispatch_bio_list
• function cmp_stripe
• function dispatch_defer_bios
• function flush_deferred_bios
• function defer_issue_bios
• function ops_run_io
• function async_copy_data
• function bio_for_each_segment
• function ops_complete_biofill
• function ops_run_biofill
• function mark_target_uptodate

Annotated Snippet

module_init(raid5_init);
module_exit(raid5_exit);
MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("RAID4/5/6 (striping with parity) personality for MD");
MODULE_ALIAS("md-personality-4"); /* RAID5 */
MODULE_ALIAS("md-raid5");
MODULE_ALIAS("md-raid4");
MODULE_ALIAS("md-level-5");
MODULE_ALIAS("md-level-4");
MODULE_ALIAS("md-personality-8"); /* RAID6 */
MODULE_ALIAS("md-raid6");
MODULE_ALIAS("md-level-6");

/* This used to be two separate modules, they were: */
MODULE_ALIAS("raid5");
MODULE_ALIAS("raid6");

Annotation

• Immediate include surface: `linux/blkdev.h`, `linux/kthread.h`, `linux/raid/pq.h`, `linux/async_tx.h`, `linux/module.h`, `linux/async.h`, `linux/seq_file.h`, `linux/cpu.h`.
• Detected declarations: `struct stripe_request_ctx`, `struct raid5_plug_cb`, `enum stripe_result`, `enum reshape_loc`, `function stripe_hash_locks_hash`, `function lock_device_hash_lock`, `function unlock_device_hash_lock`, `function lock_all_device_hash_locks_irq`, `function unlock_all_device_hash_locks_irq`, `function raid6_d0`.
• 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.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.