fs/ocfs2/stackglue.c

File Facts

System

Linux kernel

Corpus path

fs/ocfs2/stackglue.c

Extension

.c

Size

16851 bytes

Lines

702

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.
• 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

• linux/list.h
• linux/spinlock.h
• linux/string.h
• linux/module.h
• linux/slab.h
• linux/kmod.h
• linux/fs.h
• linux/kobject.h
• linux/sysfs.h
• linux/sysctl.h
• ocfs2_fs.h
• stackglue.h

Detected Declarations

• function list_for_each_entry
• function ocfs2_stack_driver_request
• function ocfs2_stack_driver_get
• function ocfs2_stack_driver_put
• function ocfs2_stack_glue_register
• function ocfs2_stack_glue_unregister
• function ocfs2_stack_glue_set_max_proto_version
• function list_for_each_entry
• function ocfs2_dlm_lock
• function ocfs2_dlm_unlock
• function ocfs2_dlm_lock_status
• function ocfs2_dlm_lvb_valid
• function ocfs2_dlm_dump_lksb
• function ocfs2_stack_supports_plocks
• function ocfs2_plock
• function ocfs2_cluster_connect
• function ocfs2_cluster_connect_agnostic
• function ocfs2_cluster_disconnect
• function program
• function ocfs2_cluster_disconnect
• function ocfs2_cluster_this_node
• function ocfs2_max_locking_protocol_show
• function ocfs2_loaded_cluster_plugins_show
• function ocfs2_active_cluster_plugin_show
• function ocfs2_cluster_stack_show
• function ocfs2_cluster_stack_store
• function ocfs2_dlm_recover_show
• function ocfs2_sysfs_exit
• function ocfs2_sysfs_init
• function ocfs2_stack_glue_init
• function ocfs2_stack_glue_exit
• module init ocfs2_stack_glue_init
• export ocfs2_stack_glue_register
• export ocfs2_stack_glue_unregister
• export ocfs2_stack_glue_set_max_proto_version
• export ocfs2_dlm_lock
• export ocfs2_dlm_unlock
• export ocfs2_dlm_lock_status
• export ocfs2_dlm_lvb_valid
• export ocfs2_dlm_lvb
• export ocfs2_dlm_dump_lksb
• export ocfs2_stack_supports_plocks
• export ocfs2_plock
• export ocfs2_cluster_connect
• export ocfs2_cluster_connect_agnostic
• export ocfs2_cluster_disconnect
• export ocfs2_cluster_hangup
• export ocfs2_cluster_this_node

Annotated Snippet

module_init(ocfs2_stack_glue_init);
module_exit(ocfs2_stack_glue_exit);

Annotation

• Immediate include surface: `linux/list.h`, `linux/spinlock.h`, `linux/string.h`, `linux/module.h`, `linux/slab.h`, `linux/kmod.h`, `linux/fs.h`, `linux/kobject.h`.
• Detected declarations: `function list_for_each_entry`, `function ocfs2_stack_driver_request`, `function ocfs2_stack_driver_get`, `function ocfs2_stack_driver_put`, `function ocfs2_stack_glue_register`, `function ocfs2_stack_glue_unregister`, `function ocfs2_stack_glue_set_max_proto_version`, `function list_for_each_entry`, `function ocfs2_dlm_lock`, `function ocfs2_dlm_unlock`.
• Atlas domain: Core OS / VFS And Filesystem Core.
• 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.