drivers/md/dm-integrity.c

File Facts

System

Linux kernel

Corpus path

drivers/md/dm-integrity.c

Extension

.c

Size

162551 bytes

Lines

5476

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

• dm-bio-record.h
• linux/compiler.h
• linux/module.h
• linux/device-mapper.h
• linux/dm-io.h
• linux/vmalloc.h
• linux/sort.h
• linux/rbtree.h
• linux/delay.h
• linux/hex.h
• linux/random.h
• linux/reboot.h
• crypto/hash.h
• crypto/skcipher.h
• crypto/utils.h
• linux/async_tx.h
• linux/dm-bufio.h
• dm-audit.h

Detected Declarations

• struct superblock
• struct journal_entry
• struct journal_sector
• struct journal_node
• struct alg_spec
• struct dm_integrity_c
• struct dm_integrity_range
• struct dm_integrity_io
• struct journal_completion
• struct journal_io
• struct bitmap_block_status
• struct flush_request
• function prev_commit_seq
• function next_commit_seq
• function dm_integrity_io_error
• function dm_integrity_failed
• function dm_integrity_disable_recalculate
• function dm_integrity_commit_id
• function get_area_and_offset
• function get_metadata_sector_and_offset
• function get_data_sector
• function wraparound_section
• function sb_set_version
• function sb_mac
• function sync_rw_sb
• function block_bitmap_op
• function block_bitmap_copy
• function access_journal_check
• function page_list_location
• function section_mac
• function rw_section_mac
• function complete_journal_op
• function xor_journal
• function complete_journal_encrypt
• function do_crypt
• function crypt_journal
• function encrypt_journal
• function complete_journal_io
• function rw_journal_sectors
• function rw_journal
• function write_journal
• function copy_from_journal
• function ranges_overlap
• function add_new_range
• function list_for_each_entry
• function remove_range_unlocked
• function remove_range
• function wait_and_add_new_range

Annotated Snippet

module_init(dm_integrity_init);
module_exit(dm_integrity_exit);

MODULE_AUTHOR("Milan Broz");
MODULE_AUTHOR("Mikulas Patocka");
MODULE_DESCRIPTION(DM_NAME " target for integrity tags extension");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `dm-bio-record.h`, `linux/compiler.h`, `linux/module.h`, `linux/device-mapper.h`, `linux/dm-io.h`, `linux/vmalloc.h`, `linux/sort.h`, `linux/rbtree.h`.
• Detected declarations: `struct superblock`, `struct journal_entry`, `struct journal_sector`, `struct journal_node`, `struct alg_spec`, `struct dm_integrity_c`, `struct dm_integrity_range`, `struct dm_integrity_io`, `struct journal_completion`, `struct journal_io`.
• 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.