fs/exfat/file.c

File Facts

System

Linux kernel

Corpus path

fs/exfat/file.c

Extension

.c

Size

24244 bytes

Lines

980

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.
• Touches user memory; correctness depends on fault-safe copying and privilege boundary handling.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/slab.h
• linux/compat.h
• linux/cred.h
• linux/buffer_head.h
• linux/blkdev.h
• linux/fsnotify.h
• linux/security.h
• linux/msdos_fs.h
• linux/writeback.h
• linux/filelock.h
• linux/falloc.h
• linux/fileattr.h
• linux/iomap.h
• exfat_raw.h
• exfat_fs.h
• iomap.h

Detected Declarations

• function Copyright
• function length
• function exfat_allow_set_time
• function exfat_sanitize_mode
• function __exfat_truncate
• function exfat_truncate
• function exfat_getattr
• function exfat_fileattr_get
• function exfat_setattr
• function exfat_allow_set_time
• function exfat_ioctl_get_attributes
• function exfat_ioctl_set_attributes
• function exfat_ioctl_fitrim
• function exfat_ioctl_shutdown
• function exfat_ioctl_get_volume_label
• function exfat_ioctl_set_volume_label
• function exfat_ioctl
• function exfat_compat_ioctl
• function exfat_file_fsync
• function exfat_extend_valid_size
• function exfat_fallback_buffered_write
• function exfat_dio_write_iter
• function exfat_file_write_iter
• function exfat_file_read_iter
• function exfat_page_mkwrite
• function exfat_file_mmap_prepare
• function exfat_splice_read
• function exfat_file_open
• function exfat_file_llseek

Annotated Snippet

const struct file_operations exfat_file_operations = {
	.open		= exfat_file_open,
	.llseek		= exfat_file_llseek,
	.read_iter	= exfat_file_read_iter,
	.write_iter	= exfat_file_write_iter,
	.unlocked_ioctl = exfat_ioctl,
#ifdef CONFIG_COMPAT
	.compat_ioctl = exfat_compat_ioctl,
#endif
	.mmap_prepare	= exfat_file_mmap_prepare,
	.fsync		= exfat_file_fsync,
	.splice_read	= exfat_splice_read,
	.splice_write	= iter_file_splice_write,
	.fallocate	= exfat_fallocate,
	.setlease	= generic_setlease,
};

const struct inode_operations exfat_file_inode_operations = {
	.setattr	= exfat_setattr,
	.getattr	= exfat_getattr,
	.fileattr_get	= exfat_fileattr_get,
};

Annotation

• Immediate include surface: `linux/slab.h`, `linux/compat.h`, `linux/cred.h`, `linux/buffer_head.h`, `linux/blkdev.h`, `linux/fsnotify.h`, `linux/security.h`, `linux/msdos_fs.h`.
• Detected declarations: `function Copyright`, `function length`, `function exfat_allow_set_time`, `function exfat_sanitize_mode`, `function __exfat_truncate`, `function exfat_truncate`, `function exfat_getattr`, `function exfat_fileattr_get`, `function exfat_setattr`, `function exfat_allow_set_time`.
• Atlas domain: Core OS / VFS And Filesystem Core.
• Implementation status: pattern implementation candidate.
• This snippet crosses the user/kernel memory boundary; validate fault handling and access checks before translating the pattern.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.