rust/kernel/debugfs/file_ops.rs
Source file repositories/reference/linux-study-clean/rust/kernel/debugfs/file_ops.rs
File Facts
- System
- Linux kernel
- Corpus path
rust/kernel/debugfs/file_ops.rs- Extension
.rs- Size
- 13462 bytes
- Lines
- 389
- Domain
- Rust Kernel Layer
- Bucket
- Rust API Membrane
- Inferred role
- Rust Kernel Layer: implementation source
- Status
- source implementation candidate
Why This File Exists
Rust-side wrappers and abstractions around kernel C APIs, ownership contracts, allocation, synchronization, and module integration.
- Rust-side wrappers and abstractions around kernel C APIs, ownership contracts, allocation, synchronization, and module integration.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
function Err
Annotated Snippet
if let Err(e) = data.read_from_slice(&mut reader) {
return e.to_errno() as isize;
}
count as isize
}
/// # Safety
///
/// `file` must be a valid pointer to a `file` struct.
/// The `private_data` of the file must contain a valid pointer to a `seq_file` whose
/// `private` data in turn points to a `T` that implements `Reader`.
/// `buf` must be a valid user-space buffer.
pub(crate) unsafe extern "C" fn write<T: Reader + Sync>(
file: *mut bindings::file,
buf: *const c_char,
count: usize,
_ppos: *mut bindings::loff_t,
) -> isize {
// SAFETY: The file was opened with `single_open`, which sets `private_data` to a `seq_file`.
let seq = unsafe { &mut *((*file).private_data.cast::<bindings::seq_file>()) };
// SAFETY: By caller precondition, this pointer is live and points to a value of type `T`.
let data = unsafe { &*(seq.private as *const T) };
read(data, buf, count)
}
// A trait to get the file operations for a type.
pub(crate) trait ReadWriteFile<T> {
const FILE_OPS: FileOps<T>;
}
impl<T: Writer + Reader + Sync> ReadWriteFile<T> for T {
const FILE_OPS: FileOps<T> = {
let operations = bindings::file_operations {
open: Some(writer_open::<T>),
read: Some(bindings::seq_read),
write: Some(write::<T>),
llseek: Some(bindings::seq_lseek),
release: Some(bindings::single_release),
..pin_init::zeroed()
};
// SAFETY: `operations` is all stock `seq_file` implementations except for `writer_open`
// and `write`.
// `writer_open`'s only requirement beyond what is provided to all open functions is that
// the inode's data pointer must point to a `T` that will outlive it, which matches the
// `FileOps` requirements.
// `write` only requires that the file's private data pointer points to `seq_file`
// which points to a `T` that will outlive it, which matches what `writer_open`
// provides.
unsafe { FileOps::new(operations, 0o600) }
};
}
/// # Safety
///
/// `inode` must be a valid pointer to an `inode` struct.
/// `file` must be a valid pointer to a `file` struct.
unsafe extern "C" fn write_only_open(
inode: *mut bindings::inode,
file: *mut bindings::file,
) -> c_int {
// SAFETY: The caller ensures that `inode` and `file` are valid pointers.
unsafe { (*file).private_data = (*inode).i_private };
0
}
/// # Safety
///
/// * `file` must be a valid pointer to a `file` struct.
/// * The `private_data` of the file must contain a valid pointer to a `T` that implements
/// `Reader`.
/// * `buf` must be a valid user-space buffer.
pub(crate) unsafe extern "C" fn write_only_write<T: Reader + Sync>(
file: *mut bindings::file,
buf: *const c_char,
count: usize,
_ppos: *mut bindings::loff_t,
) -> isize {
// SAFETY: The caller ensures that `file` is a valid pointer and that `private_data` holds a
// valid pointer to `T`.
let data = unsafe { &*((*file).private_data as *const T) };
read(data, buf, count)
}
pub(crate) trait WriteFile<T> {
const FILE_OPS: FileOps<T>;
}
impl<T: Reader + Sync> WriteFile<T> for T {
const FILE_OPS: FileOps<T> = {
Annotation
- Detected declarations: `function Err`.
- Atlas domain: Rust Kernel Layer / Rust API Membrane.
- Implementation status: source 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.