fs/hfs/dir.c

File Facts

System

Linux kernel

Corpus path

fs/hfs/dir.c

Extension

.c

Size

8268 bytes

Lines

332

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

• hfs_fs.h
• btree.h

Detected Declarations

• function Copyright
• function hfs_readdir
• function hfs_dir_release
• function hfs_create
• function hfs_mkdir
• function hfs_remove
• function hfs_rename

Annotated Snippet

const struct file_operations hfs_dir_operations = {
	.read		= generic_read_dir,
	.iterate_shared	= hfs_readdir,
	.llseek		= generic_file_llseek,
	.release	= hfs_dir_release,
};

const struct inode_operations hfs_dir_inode_operations = {
	.create		= hfs_create,
	.lookup		= hfs_lookup,
	.unlink		= hfs_remove,
	.mkdir		= hfs_mkdir,
	.rmdir		= hfs_remove,
	.rename		= hfs_rename,
	.setattr	= hfs_inode_setattr,
	.fileattr_get	= hfs_fileattr_get,
};

Annotation

• Immediate include surface: `hfs_fs.h`, `btree.h`.
• Detected declarations: `function Copyright`, `function hfs_readdir`, `function hfs_dir_release`, `function hfs_create`, `function hfs_mkdir`, `function hfs_remove`, `function hfs_rename`.
• 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.