fs/qnx6/dir.c

File Facts

System

Linux kernel

Corpus path

fs/qnx6/dir.c

Extension

.c

Size

7027 bytes

Lines

285

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
• qnx6.h

Detected Declarations

• function qnx6_lfile_checksum
• function last_entry
• function qnx6_dir_longfilename
• function qnx6_readdir
• function qnx6_long_match
• function qnx6_match
• function qnx6_find_ino

Annotated Snippet

const struct file_operations qnx6_dir_operations = {
	.llseek		= generic_file_llseek,
	.read		= generic_read_dir,
	.iterate_shared	= qnx6_readdir,
	.fsync		= simple_fsync,
	.setlease	= generic_setlease,
};

const struct inode_operations qnx6_dir_inode_operations = {
	.lookup		= qnx6_lookup,
};

Annotation

• Immediate include surface: `linux/filelock.h`, `qnx6.h`.
• Detected declarations: `function qnx6_lfile_checksum`, `function last_entry`, `function qnx6_dir_longfilename`, `function qnx6_readdir`, `function qnx6_long_match`, `function qnx6_match`, `function qnx6_find_ino`.
• 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.