mm/fs: remove truncate_range
Remove vmtruncate_range(), and remove the truncate_range method from struct inode_operations: only tmpfs ever supported it, and tmpfs has now converted over to using the fallocate method of file_operations. Update Documentation accordingly, adding (setlease and) fallocate lines. And while we're in mm.h, remove duplicate declarations of shmem_lock() and shmem_file_setup(): everyone is now using the ones in shmem_fs.h. Based-on-patch-by:Cong Wang <amwang@redhat.com> Signed-off-by:
Hugh Dickins <hughd@google.com> Cc: Christoph Hellwig <hch@infradead.org> Cc: Cong Wang <amwang@redhat.com> Cc: Al Viro <viro@zeniv.linux.org.uk> Signed-off-by:
Andrew Morton <akpm@linux-foundation.org> Signed-off-by:
Linus Torvalds <torvalds@linux-foundation.org>
Showing
- Documentation/filesystems/Locking 0 additions, 2 deletionsDocumentation/filesystems/Locking
- Documentation/filesystems/vfs.txt 8 additions, 5 deletionsDocumentation/filesystems/vfs.txt
- fs/bad_inode.c 0 additions, 1 deletionfs/bad_inode.c
- include/linux/fs.h 0 additions, 1 deletioninclude/linux/fs.h
- include/linux/mm.h 0 additions, 4 deletionsinclude/linux/mm.h
- mm/shmem.c 0 additions, 1 deletionmm/shmem.c
- mm/truncate.c 0 additions, 25 deletionsmm/truncate.c
Loading
Please register or sign in to comment