fs/orangefs/dir.c

File Facts

System

Linux kernel

Corpus path

fs/orangefs/dir.c

Extension

.c

Size

9180 bytes

Lines

398

Domain

Core OS

Bucket

VFS And Filesystem Core

Inferred role

Core OS: operation-table or driver-model contract

Status

pattern 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 an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• 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/filelock.h
• protocol.h
• orangefs-kernel.h
• orangefs-bufmap.h

Detected Declarations

• struct orangefs_dir_part
• struct orangefs_dir
• function pointer
• function parse_readdir
• function orangefs_dir_more
• function fill_from_part
• function orangefs_dir_fill
• function orangefs_dir_llseek
• function orangefs_dir_iterate
• function orangefs_dir_open
• function orangefs_dir_release

Annotated Snippet

const struct file_operations orangefs_dir_operations = {
	.llseek = orangefs_dir_llseek,
	.read = generic_read_dir,
	.iterate_shared = orangefs_dir_iterate,
	.open = orangefs_dir_open,
	.release = orangefs_dir_release,
	.setlease = generic_setlease,
};

Annotation

• Immediate include surface: `linux/filelock.h`, `protocol.h`, `orangefs-kernel.h`, `orangefs-bufmap.h`.
• Detected declarations: `struct orangefs_dir_part`, `struct orangefs_dir`, `function pointer`, `function parse_readdir`, `function orangefs_dir_more`, `function fill_from_part`, `function orangefs_dir_fill`, `function orangefs_dir_llseek`, `function orangefs_dir_iterate`, `function orangefs_dir_open`.
• Atlas domain: Core OS / VFS And Filesystem Core.
• Implementation status: pattern 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.