fs/nfs/io.c
Source file repositories/reference/linux-study-clean/fs/nfs/io.c
File Facts
- System
- Linux kernel
- Corpus path
fs/nfs/io.c- Extension
.c- Size
- 4244 bytes
- Lines
- 164
- Domain
- Core OS
- Bucket
- VFS And Filesystem Core
- Inferred role
- Core OS: exported/initcall integration point
- Status
- integration 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.
- Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/types.hlinux/kernel.hlinux/bitops.hlinux/rwsem.hlinux/fs.hlinux/nfs_fs.hinternal.h
Detected Declarations
function Copyrightfunction nfs_end_io_readfunction nfs_start_io_writefunction nfs_end_io_writefunction nfs_block_bufferedfunction nfs_start_io_directfunction nfs_end_io_directexport nfs_start_io_writeexport nfs_end_io_write
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/*
* Copyright (c) 2016 Trond Myklebust
*
* I/O and data path helper functionality.
*/
#include <linux/types.h>
#include <linux/kernel.h>
#include <linux/bitops.h>
#include <linux/rwsem.h>
#include <linux/fs.h>
#include <linux/nfs_fs.h>
#include "internal.h"
/**
* nfs_start_io_read - declare the file is being used for buffered reads
* @inode: file inode
*
* Declare that a buffered read operation is about to start, and ensure
* that we block all direct I/O.
* On exit, the function ensures that the NFS_INO_ODIRECT flag is unset,
* and holds a shared lock on inode->i_rwsem to ensure that the flag
* cannot be changed.
* In practice, this means that buffered read operations are allowed to
* execute in parallel, thanks to the shared lock, whereas direct I/O
* operations need to wait to grab an exclusive lock in order to set
* NFS_INO_ODIRECT.
* Note that buffered writes and truncates both take a write lock on
* inode->i_rwsem, meaning that those are serialised w.r.t. the reads.
*/
int
nfs_start_io_read(struct inode *inode)
{
struct nfs_inode *nfsi = NFS_I(inode);
int err;
/* Be an optimist! */
err = down_read_killable(&inode->i_rwsem);
if (err)
return err;
if (test_bit(NFS_INO_ODIRECT, &nfsi->flags) == 0)
return 0;
up_read(&inode->i_rwsem);
/* Slow path.... */
err = down_write_killable(&inode->i_rwsem);
if (err)
return err;
nfs_file_block_o_direct(nfsi);
downgrade_write(&inode->i_rwsem);
return 0;
}
/**
* nfs_end_io_read - declare that the buffered read operation is done
* @inode: file inode
*
* Declare that a buffered read operation is done, and release the shared
* lock on inode->i_rwsem.
*/
void
nfs_end_io_read(struct inode *inode)
{
up_read(&inode->i_rwsem);
}
/**
* nfs_start_io_write - declare the file is being used for buffered writes
* @inode: file inode
*
* Declare that a buffered read operation is about to start, and ensure
* that we block all direct I/O.
*/
int
nfs_start_io_write(struct inode *inode)
{
int err;
err = down_write_killable(&inode->i_rwsem);
if (!err)
nfs_file_block_o_direct(NFS_I(inode));
return err;
}
EXPORT_SYMBOL_GPL(nfs_start_io_write);
/**
* nfs_end_io_write - declare that the buffered write operation is done
Annotation
- Immediate include surface: `linux/types.h`, `linux/kernel.h`, `linux/bitops.h`, `linux/rwsem.h`, `linux/fs.h`, `linux/nfs_fs.h`, `internal.h`.
- Detected declarations: `function Copyright`, `function nfs_end_io_read`, `function nfs_start_io_write`, `function nfs_end_io_write`, `function nfs_block_buffered`, `function nfs_start_io_direct`, `function nfs_end_io_direct`, `export nfs_start_io_write`, `export nfs_end_io_write`.
- Atlas domain: Core OS / VFS And Filesystem Core.
- Implementation status: integration 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.