fs/ntfs3/dir.c

File Facts

System

Linux kernel

Corpus path

fs/ntfs3/dir.c

Extension

.c

Size

14914 bytes

Lines

680

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/fs.h
• linux/filelock.h
• linux/nls.h
• debug.h
• ntfs.h
• ntfs_fs.h

Detected Declarations

• function Copyright
• function put_utf16
• function _utf8s_to_utf16s
• function ntfs_nls_to_utf16
• function ntfs_dir_emit
• function ntfs_read_hdr
• function ntfs_readdir
• function ntfs_dir_count
• function dir_is_empty

Annotated Snippet

const struct file_operations ntfs_dir_operations = {
	.llseek		= generic_file_llseek,
	.read		= generic_read_dir,
	.iterate_shared	= ntfs_readdir,
	.fsync		= ntfs_file_fsync,
	.open		= ntfs_file_open,
	.unlocked_ioctl = ntfs_ioctl,
#ifdef CONFIG_COMPAT
	.compat_ioctl   = ntfs_compat_ioctl,
#endif
	.setlease	= generic_setlease,
};
// clang-format on

Annotation

• Immediate include surface: `linux/fs.h`, `linux/filelock.h`, `linux/nls.h`, `debug.h`, `ntfs.h`, `ntfs_fs.h`.
• Detected declarations: `function Copyright`, `function put_utf16`, `function _utf8s_to_utf16s`, `function ntfs_nls_to_utf16`, `function ntfs_dir_emit`, `function ntfs_read_hdr`, `function ntfs_readdir`, `function ntfs_dir_count`, `function dir_is_empty`.
• 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.