5d5d568975
All places outside of core VFS that checked ->read and ->write for being NULL or
called the methods directly are gone now, so NULL {read,write} with non-NULL
{read,write}_iter will do the right thing in all cases.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
46 lines
1.3 KiB
C
46 lines
1.3 KiB
C
/* file-mmu.c: ramfs MMU-based file operations
|
|
*
|
|
* Resizable simple ram filesystem for Linux.
|
|
*
|
|
* Copyright (C) 2000 Linus Torvalds.
|
|
* 2000 Transmeta Corp.
|
|
*
|
|
* Usage limits added by David Gibson, Linuxcare Australia.
|
|
* This file is released under the GPL.
|
|
*/
|
|
|
|
/*
|
|
* NOTE! This filesystem is probably most useful
|
|
* not as a real filesystem, but as an example of
|
|
* how virtual filesystems can be written.
|
|
*
|
|
* It doesn't get much simpler than this. Consider
|
|
* that this file implements the full semantics of
|
|
* a POSIX-compliant read-write filesystem.
|
|
*
|
|
* Note in particular how the filesystem does not
|
|
* need to implement any data structures of its own
|
|
* to keep track of the virtual data: using the VFS
|
|
* caches is sufficient.
|
|
*/
|
|
|
|
#include <linux/fs.h>
|
|
#include <linux/mm.h>
|
|
#include <linux/ramfs.h>
|
|
|
|
#include "internal.h"
|
|
|
|
const struct file_operations ramfs_file_operations = {
|
|
.read_iter = generic_file_read_iter,
|
|
.write_iter = generic_file_write_iter,
|
|
.mmap = generic_file_mmap,
|
|
.fsync = noop_fsync,
|
|
.splice_read = generic_file_splice_read,
|
|
.splice_write = iter_file_splice_write,
|
|
.llseek = generic_file_llseek,
|
|
};
|
|
|
|
const struct inode_operations ramfs_file_inode_operations = {
|
|
.setattr = simple_setattr,
|
|
.getattr = simple_getattr,
|
|
};
|