fs/dlm/main.c

File Facts

System

Linux kernel

Corpus path

fs/dlm/main.c

Extension

.c

Size

2110 bytes

Lines

106

Domain

Core OS

Bucket

VFS And Filesystem Core

Inferred role

Core OS: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• dlm_internal.h
• lockspace.h
• lock.h
• user.h
• memory.h
• config.h
• midcomms.h
• trace/events/dlm.h

Detected Declarations

• function init_dlm
• function exit_dlm
• module init init_dlm
• export dlm_new_lockspace
• export dlm_release_lockspace
• export dlm_lock
• export dlm_unlock

Annotated Snippet

module_init(init_dlm);
module_exit(exit_dlm);

MODULE_DESCRIPTION("Distributed Lock Manager");
MODULE_AUTHOR("Red Hat, Inc.");
MODULE_LICENSE("GPL");

EXPORT_SYMBOL_GPL(dlm_new_lockspace);
EXPORT_SYMBOL_GPL(dlm_release_lockspace);
EXPORT_SYMBOL_GPL(dlm_lock);
EXPORT_SYMBOL_GPL(dlm_unlock);

Annotation

• Immediate include surface: `linux/module.h`, `dlm_internal.h`, `lockspace.h`, `lock.h`, `user.h`, `memory.h`, `config.h`, `midcomms.h`.
• Detected declarations: `function init_dlm`, `function exit_dlm`, `module init init_dlm`, `export dlm_new_lockspace`, `export dlm_release_lockspace`, `export dlm_lock`, `export dlm_unlock`.
• Atlas domain: Core OS / VFS And Filesystem Core.
• Implementation status: integration 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.