fs/udf/dir.c

File Facts

System

Linux kernel

Corpus path

fs/udf/dir.c

Extension

.c

Size

4095 bytes

Lines

163

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

• udfdecl.h
• linux/string.h
• linux/errno.h
• linux/filelock.h
• linux/mm.h
• linux/slab.h
• linux/bio.h
• linux/iversion.h
• udf_i.h
• udf_sb.h

Detected Declarations

• function udf_readdir
• function readdir
• function udf_dir_open
• function udf_dir_release
• function udf_dir_llseek

Annotated Snippet

const struct file_operations udf_dir_operations = {
	.open			= udf_dir_open,
	.release		= udf_dir_release,
	.llseek			= udf_dir_llseek,
	.read			= generic_read_dir,
	.iterate_shared		= udf_readdir,
	.unlocked_ioctl		= udf_ioctl,
	.fsync			= udf_fsync,
	.setlease		= generic_setlease,
};

Annotation

• Immediate include surface: `udfdecl.h`, `linux/string.h`, `linux/errno.h`, `linux/filelock.h`, `linux/mm.h`, `linux/slab.h`, `linux/bio.h`, `linux/iversion.h`.
• Detected declarations: `function udf_readdir`, `function readdir`, `function udf_dir_open`, `function udf_dir_release`, `function udf_dir_llseek`.
• 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.