Commit 50c1f43a authored by Tobin C. Harding's avatar Tobin C. Harding Committed by Jonathan Corbet

docs: filesystems: vfs: Remove space before tab

Currently the file has a bunch of spaces before tabspaces.  This is a
nuisance when patching the file because they show up whenever we touch
these lines.  Let's just fix them all now in preparation for doing the
RST conversion.

Remove spaces before tabspaces.
Tested-by: default avatarRandy Dunlap <rdunlap@infradead.org>
Signed-off-by: default avatarTobin C. Harding <tobin@kernel.org>
Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
parent 93285c01
...@@ -134,7 +134,7 @@ struct file_system_type { ...@@ -134,7 +134,7 @@ struct file_system_type {
should be shut down should be shut down
owner: for internal VFS use: you should initialize this to THIS_MODULE in owner: for internal VFS use: you should initialize this to THIS_MODULE in
most cases. most cases.
next: for internal VFS use: you should initialize this to NULL next: for internal VFS use: you should initialize this to NULL
...@@ -143,7 +143,7 @@ struct file_system_type { ...@@ -143,7 +143,7 @@ struct file_system_type {
The mount() method has the following arguments: The mount() method has the following arguments:
struct file_system_type *fs_type: describes the filesystem, partly initialized struct file_system_type *fs_type: describes the filesystem, partly initialized
by the specific filesystem code by the specific filesystem code
int flags: mount flags int flags: mount flags
...@@ -180,12 +180,12 @@ and provides a fill_super() callback instead. The generic variants are: ...@@ -180,12 +180,12 @@ and provides a fill_super() callback instead. The generic variants are:
mount_nodev: mount a filesystem that is not backed by a device mount_nodev: mount a filesystem that is not backed by a device
mount_single: mount a filesystem which shares the instance between mount_single: mount a filesystem which shares the instance between
all mounts all mounts
A fill_super() callback implementation has the following arguments: A fill_super() callback implementation has the following arguments:
struct super_block *sb: the superblock structure. The callback struct super_block *sb: the superblock structure. The callback
must initialize this properly. must initialize this properly.
void *data: arbitrary mount options, usually comes as an ASCII void *data: arbitrary mount options, usually comes as an ASCII
string (see "Mount Options" section) string (see "Mount Options" section)
...@@ -236,14 +236,14 @@ only called from a process context (i.e. not from an interrupt handler ...@@ -236,14 +236,14 @@ only called from a process context (i.e. not from an interrupt handler
or bottom half). or bottom half).
alloc_inode: this method is called by alloc_inode() to allocate memory alloc_inode: this method is called by alloc_inode() to allocate memory
for struct inode and initialize it. If this function is not for struct inode and initialize it. If this function is not
defined, a simple 'struct inode' is allocated. Normally defined, a simple 'struct inode' is allocated. Normally
alloc_inode will be used to allocate a larger structure which alloc_inode will be used to allocate a larger structure which
contains a 'struct inode' embedded within it. contains a 'struct inode' embedded within it.
destroy_inode: this method is called by destroy_inode() to release destroy_inode: this method is called by destroy_inode() to release
resources allocated for struct inode. It is only required if resources allocated for struct inode. It is only required if
->alloc_inode was defined and simply undoes anything done by ->alloc_inode was defined and simply undoes anything done by
->alloc_inode. ->alloc_inode.
dirty_inode: this method is called by the VFS to mark an inode dirty. dirty_inode: this method is called by the VFS to mark an inode dirty.
...@@ -271,15 +271,15 @@ or bottom half). ...@@ -271,15 +271,15 @@ or bottom half).
(i.e. unmount). This is called with the superblock lock held (i.e. unmount). This is called with the superblock lock held
sync_fs: called when VFS is writing out all dirty data associated with sync_fs: called when VFS is writing out all dirty data associated with
a superblock. The second parameter indicates whether the method a superblock. The second parameter indicates whether the method
should wait until the write out has been completed. Optional. should wait until the write out has been completed. Optional.
freeze_fs: called when VFS is locking a filesystem and freeze_fs: called when VFS is locking a filesystem and
forcing it into a consistent state. This method is currently forcing it into a consistent state. This method is currently
used by the Logical Volume Manager (LVM). used by the Logical Volume Manager (LVM).
unfreeze_fs: called when VFS is unlocking a filesystem and making it writable unfreeze_fs: called when VFS is unlocking a filesystem and making it writable
again. again.
statfs: called when the VFS needs to get filesystem statistics. statfs: called when the VFS needs to get filesystem statistics.
...@@ -476,30 +476,30 @@ otherwise noted. ...@@ -476,30 +476,30 @@ otherwise noted.
that. that.
permission: called by the VFS to check for access rights on a POSIX-like permission: called by the VFS to check for access rights on a POSIX-like
filesystem. filesystem.
May be called in rcu-walk mode (mask & MAY_NOT_BLOCK). If in rcu-walk May be called in rcu-walk mode (mask & MAY_NOT_BLOCK). If in rcu-walk
mode, the filesystem must check the permission without blocking or mode, the filesystem must check the permission without blocking or
storing to the inode. storing to the inode.
If a situation is encountered that rcu-walk cannot handle, return If a situation is encountered that rcu-walk cannot handle, return
-ECHILD and it will be called again in ref-walk mode. -ECHILD and it will be called again in ref-walk mode.
setattr: called by the VFS to set attributes for a file. This method setattr: called by the VFS to set attributes for a file. This method
is called by chmod(2) and related system calls. is called by chmod(2) and related system calls.
getattr: called by the VFS to get attributes of a file. This method getattr: called by the VFS to get attributes of a file. This method
is called by stat(2) and related system calls. is called by stat(2) and related system calls.
listxattr: called by the VFS to list all extended attributes for a listxattr: called by the VFS to list all extended attributes for a
given file. This method is called by the listxattr(2) system call. given file. This method is called by the listxattr(2) system call.
update_time: called by the VFS to update a specific time or the i_version of update_time: called by the VFS to update a specific time or the i_version of
an inode. If this is not defined the VFS will update the inode itself an inode. If this is not defined the VFS will update the inode itself
and call mark_inode_dirty_sync. and call mark_inode_dirty_sync.
atomic_open: called on the last component of an open. Using this optional atomic_open: called on the last component of an open. Using this optional
method the filesystem can look up, possibly create and open the file in method the filesystem can look up, possibly create and open the file in
one atomic operation. If it wants to leave actual opening to the one atomic operation. If it wants to leave actual opening to the
caller (e.g. if the file turned out to be a symlink, device, or just caller (e.g. if the file turned out to be a symlink, device, or just
something filesystem won't do atomic open for), it may signal this by something filesystem won't do atomic open for), it may signal this by
...@@ -687,13 +687,13 @@ struct address_space_operations { ...@@ -687,13 +687,13 @@ struct address_space_operations {
that all succeeds, ->readpage will be called again. that all succeeds, ->readpage will be called again.
writepages: called by the VM to write out pages associated with the writepages: called by the VM to write out pages associated with the
address_space object. If wbc->sync_mode is WBC_SYNC_ALL, then address_space object. If wbc->sync_mode is WBC_SYNC_ALL, then
the writeback_control will specify a range of pages that must be the writeback_control will specify a range of pages that must be
written out. If it is WBC_SYNC_NONE, then a nr_to_write is given written out. If it is WBC_SYNC_NONE, then a nr_to_write is given
and that many pages should be written if possible. and that many pages should be written if possible.
If no ->writepages is given, then mpage_writepages is used If no ->writepages is given, then mpage_writepages is used
instead. This will choose pages from the address space that are instead. This will choose pages from the address space that are
tagged as DIRTY and will pass them to ->writepage. tagged as DIRTY and will pass them to ->writepage.
set_page_dirty: called by the VM to set a page dirty. set_page_dirty: called by the VM to set a page dirty.
This is particularly needed if an address space attaches This is particularly needed if an address space attaches
...@@ -704,11 +704,11 @@ struct address_space_operations { ...@@ -704,11 +704,11 @@ struct address_space_operations {
PAGECACHE_TAG_DIRTY tag in the radix tree. PAGECACHE_TAG_DIRTY tag in the radix tree.
readpages: called by the VM to read pages associated with the address_space readpages: called by the VM to read pages associated with the address_space
object. This is essentially just a vector version of object. This is essentially just a vector version of
readpage. Instead of just one page, several pages are readpage. Instead of just one page, several pages are
requested. requested.
readpages is only used for read-ahead, so read errors are readpages is only used for read-ahead, so read errors are
ignored. If anything goes wrong, feel free to give up. ignored. If anything goes wrong, feel free to give up.
write_begin: write_begin:
Called by the generic buffered write code to ask the filesystem to Called by the generic buffered write code to ask the filesystem to
...@@ -745,12 +745,12 @@ struct address_space_operations { ...@@ -745,12 +745,12 @@ struct address_space_operations {
that were able to be copied into pagecache. that were able to be copied into pagecache.
bmap: called by the VFS to map a logical block offset within object to bmap: called by the VFS to map a logical block offset within object to
physical block number. This method is used by the FIBMAP physical block number. This method is used by the FIBMAP
ioctl and for working with swap-files. To be able to swap to ioctl and for working with swap-files. To be able to swap to
a file, the file must have a stable mapping to a block a file, the file must have a stable mapping to a block
device. The swap system does not go through the filesystem device. The swap system does not go through the filesystem
but instead uses bmap to find out where the blocks in the file but instead uses bmap to find out where the blocks in the file
are and uses those addresses directly. are and uses those addresses directly.
invalidatepage: If a page has PagePrivate set, then invalidatepage invalidatepage: If a page has PagePrivate set, then invalidatepage
will be called when part or all of the page is to be removed will be called when part or all of the page is to be removed
...@@ -810,7 +810,7 @@ struct address_space_operations { ...@@ -810,7 +810,7 @@ struct address_space_operations {
putback_page: Called by the VM when isolated page's migration fails. putback_page: Called by the VM when isolated page's migration fails.
launder_page: Called before freeing a page - it writes back the dirty page. To launder_page: Called before freeing a page - it writes back the dirty page. To
prevent redirtying the page, it is kept locked during the whole prevent redirtying the page, it is kept locked during the whole
operation. operation.
is_partially_uptodate: Called by the VM when reading a file through the is_partially_uptodate: Called by the VM when reading a file through the
...@@ -921,7 +921,7 @@ otherwise noted. ...@@ -921,7 +921,7 @@ otherwise noted.
unlocked_ioctl: called by the ioctl(2) system call. unlocked_ioctl: called by the ioctl(2) system call.
compat_ioctl: called by the ioctl(2) system call when 32 bit system calls compat_ioctl: called by the ioctl(2) system call when 32 bit system calls
are used on 64 bit kernels. are used on 64 bit kernels.
mmap: called by the mmap(2) system call mmap: called by the mmap(2) system call
...@@ -946,7 +946,7 @@ otherwise noted. ...@@ -946,7 +946,7 @@ otherwise noted.
(non-blocking) mode is enabled for a file (non-blocking) mode is enabled for a file
lock: called by the fcntl(2) system call for F_GETLK, F_SETLK, and F_SETLKW lock: called by the fcntl(2) system call for F_GETLK, F_SETLK, and F_SETLKW
commands commands
get_unmapped_area: called by the mmap(2) system call get_unmapped_area: called by the mmap(2) system call
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment