fs/ceph/file.c

File Facts

System

Linux kernel

Corpus path

fs/ceph/file.c

Extension

.c

Size

87797 bytes

Lines

3259

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• 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/ceph/ceph_debug.h
• linux/ceph/striper.h
• linux/module.h
• linux/sched.h
• linux/slab.h
• linux/file.h
• linux/mount.h
• linux/namei.h
• linux/writeback.h
• linux/falloc.h
• linux/iversion.h
• linux/ktime.h
• linux/splice.h
• super.h
• mds_client.h
• cache.h
• io.h
• metric.h
• subvolume_metrics.h

Detected Declarations

• struct ceph_aio_request
• struct ceph_aio_work
• function ceph_record_subvolume_io
• function ceph_flags_sys2wire
• function fsync
• function iov_iter_get_pages
• function put_bvecs
• function prepare_open_request
• function ceph_init_file_info
• function ceph_init_file
• function ceph_renew_caps
• function locally
• function cache_file_layout
• function try_prep_async_create
• function READ_ONCE
• function restore_deleg_ino
• function wake_async_create_waiters
• function ceph_async_create_cb
• function ceph_finish_async_create
• function ceph_atomic_open
• function ceph_release
• function __ceph_sync_read
• function ceph_sync_read
• function ceph_aio_complete
• function ceph_aio_complete_req
• function ceph_aio_retry_work
• function ceph_direct_read_write
• function ceph_sync_write
• function ceph_sparse_ext_map_end
• function ceph_sparse_ext_map_end
• function ceph_read_iter
• function ceph_splice_read
• function ceph_write_iter
• function ceph_llseek
• function ceph_zero_partial_page
• function ceph_zero_pagecache_range
• function ceph_zero_partial_object
• function ceph_zero_objects
• function ceph_fallocate
• function get_rd_wr_caps
• function put_rd_wr_caps
• function is_file_size_ok
• function to
• function ceph_alloc_copyfrom_request
• function ceph_do_objects_copy
• function __ceph_copy_file_range
• function copies
• function ceph_copy_file_range

Annotated Snippet

const struct file_operations ceph_file_fops = {
	.open = ceph_open,
	.release = ceph_release,
	.llseek = ceph_llseek,
	.read_iter = ceph_read_iter,
	.write_iter = ceph_write_iter,
	.mmap_prepare = ceph_mmap_prepare,
	.fsync = ceph_fsync,
	.lock = ceph_lock,
	.flock = ceph_flock,
	.splice_read = ceph_splice_read,
	.splice_write = iter_file_splice_write,
	.unlocked_ioctl = ceph_ioctl,
	.compat_ioctl = compat_ptr_ioctl,
	.fallocate	= ceph_fallocate,
	.copy_file_range = ceph_copy_file_range,
};

Annotation

• Immediate include surface: `linux/ceph/ceph_debug.h`, `linux/ceph/striper.h`, `linux/module.h`, `linux/sched.h`, `linux/slab.h`, `linux/file.h`, `linux/mount.h`, `linux/namei.h`.
• Detected declarations: `struct ceph_aio_request`, `struct ceph_aio_work`, `function ceph_record_subvolume_io`, `function ceph_flags_sys2wire`, `function fsync`, `function iov_iter_get_pages`, `function put_bvecs`, `function prepare_open_request`, `function ceph_init_file_info`, `function ceph_init_file`.
• Atlas domain: Core OS / VFS And Filesystem Core.
• Implementation status: pattern implementation candidate.
• 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.