table of contents
- wheezy 8.2-1
|VFS_MOUNT(9)||Kernel Developer's Manual||VFS_MOUNT(9)|
NAME¶vfs_mount — generic file system mount function
#include <sys/mount.h> int
vfs_mount(struct thread *td, const char *fstype, char *fspath, int fsflags, void *fsdata);
DESCRIPTION¶The vfs_mount() function handles the generic portion of mounting a file system, and calls the file system specific mount function after verifying its parameters and setting up the structures expected by the underlying mount code. vfs_mount() is called directly by the mount(2) system call. Its arguments are:
- The thread responsible for this call.
- The type of file system being mounted.
- The path to the mount point of the file system.
- Flags controlling the mount. See mount(2)
- File system specific data structure. It is in userspace when passed to vfs_mount() and is left untouched when passed to file system's mount().
RETURN VALUES¶A 0 value is returned on success.
- The fs type or the mount point path is too long or any individual path component is too long.
- Permission denied. There are a number of reason this can occur ranging from the user not having permission to mount a file system to the securelevel being to high to load the fstype module.
- Invalid operation (ex: trying to update a non mount-point).
- The mount point does not exist (from namei()).
- The mount point is a muddle of links (from namei()).
- The operation is not supported (ex: reloading a r/w file system).
- The mount point is busy or is not really a mount point (on update).
- The mount point is not a directory.
- The kernel linker was unable to load the specified fstype or was unable to find the specified fstype module.
SEE ALSO¶mount(2), mount(8) vfs.usermount
AUTHORS¶This manual page was written by Chad David ⟨email@example.com⟩.
|November 26, 2004||Debian|