include/uapi/linux/drbd.h

File Facts

System

Linux kernel

Corpus path

include/uapi/linux/drbd.h

Extension

.h

Size

11154 bytes

Lines

414

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: implementation source

Status

source implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/types.h
• asm/byteorder.h

Detected Declarations

• struct drbd_genlmsghdr
• enum drbd_io_error_p
• enum drbd_fencing_p
• enum drbd_disconnect_p
• enum drbd_after_sb_p
• enum drbd_on_no_data
• enum drbd_on_congestion
• enum drbd_read_balancing
• enum drbd_ret_code
• enum drbd_role
• enum drbd_conns
• enum drbd_disk_state
• enum drbd_state_rv
• enum drbd_uuid_index
• enum drbd_timeout_flag
• enum drbd_notification_type
• enum drbd_peer_state
• enum write_ordering_e
• enum drbd_state_info_bcast_reason

Annotated Snippet

struct drbd_genlmsghdr {
	__u32 minor;
	union {
		__u32 flags;
		__s32 ret_code;
	};
};

/* To be used in drbd_genlmsghdr.flags */
enum {
	DRBD_GENL_F_SET_DEFAULTS = 1,
};

enum drbd_state_info_bcast_reason {
	SIB_GET_STATUS_REPLY = 1,
	SIB_STATE_CHANGE = 2,
	SIB_HELPER_PRE = 3,
	SIB_HELPER_POST = 4,
	SIB_SYNC_PROGRESS = 5,
};

#endif /* _UAPI_LINUX_DRBD_H */

Annotation

• Immediate include surface: `linux/types.h`, `asm/byteorder.h`.
• Detected declarations: `struct drbd_genlmsghdr`, `enum drbd_io_error_p`, `enum drbd_fencing_p`, `enum drbd_disconnect_p`, `enum drbd_after_sb_p`, `enum drbd_on_no_data`, `enum drbd_on_congestion`, `enum drbd_read_balancing`, `enum drbd_ret_code`, `enum drbd_role`.
• Atlas domain: Core OS / Core Kernel Interface.
• Implementation status: source implementation candidate.

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.