drivers/block/drbd/drbd_proc.c

File Facts

System

Linux kernel

Corpus path

drivers/block/drbd/drbd_proc.c

Extension

.c

Size

10047 bytes

Lines

324

Domain

Driver Families

Bucket

drivers/block

Inferred role

Driver Families: implementation source

Status

source 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.
• 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/module.h
• linux/uaccess.h
• linux/fs.h
• linux/file.h
• linux/proc_fs.h
• linux/seq_file.h
• linux/drbd.h
• drbd_int.h

Detected Declarations

• function seq_printf_with_thousands_grouping
• function drbd_get_syncer_progress
• function drbd_syncer_progress
• function drbd_seq_show

Annotated Snippet

if (drbd_proc_details >= 1 && get_ldev_if_state(device, D_FAILED)) {
			lc_seq_printf_stats(seq, device->resync);
			lc_seq_printf_stats(seq, device->act_log);
			put_ldev(device);
		}

		if (drbd_proc_details >= 2)
			seq_printf(seq, "\tblocked on activity log: %d\n", atomic_read(&device->ap_actlog_cnt));
	}
	rcu_read_unlock();

	return 0;
}

Annotation

• Immediate include surface: `linux/module.h`, `linux/uaccess.h`, `linux/fs.h`, `linux/file.h`, `linux/proc_fs.h`, `linux/seq_file.h`, `linux/drbd.h`, `drbd_int.h`.
• Detected declarations: `function seq_printf_with_thousands_grouping`, `function drbd_get_syncer_progress`, `function drbd_syncer_progress`, `function drbd_seq_show`.
• Atlas domain: Driver Families / drivers/block.
• Implementation status: source 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.