fs/isofs/dir.c

File Facts

System

Linux kernel

Corpus path

fs/isofs/dir.c

Extension

.c

Size

7220 bytes

Lines

304

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/gfp.h
• linux/filelock.h
• linux/slab.h
• isofs.h
• linux/fileattr.h

Detected Declarations

• function isofs_name_translate
• function get_acorn_filename
• function do_isofs_readdir
• function isofs_readdir
• function isofs_fileattr_get

Annotated Snippet

const struct file_operations isofs_dir_operations =
{
	.llseek = generic_file_llseek,
	.read = generic_read_dir,
	.iterate_shared = isofs_readdir,
	.setlease = generic_setlease,
};

/*
 * directories can handle most operations...
 */
const struct inode_operations isofs_dir_inode_operations =
{
	.lookup = isofs_lookup,
	.fileattr_get = isofs_fileattr_get,
};

Annotation

• Immediate include surface: `linux/gfp.h`, `linux/filelock.h`, `linux/slab.h`, `isofs.h`, `linux/fileattr.h`.
• Detected declarations: `function isofs_name_translate`, `function get_acorn_filename`, `function do_isofs_readdir`, `function isofs_readdir`, `function isofs_fileattr_get`.
• 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.