Lines Matching full:filesystem

4 Filesystem Mount API
11  (2) The filesystem context.
13  (3) The filesystem context operations.
15  (4) Filesystem context security.
17  (5) VFS filesystem context API.
31  (1) Create a filesystem context.
52 The first is invoked to set up the filesystem-specific parts of a filesystem
57 Note that security initialisation is done *after* the filesystem is called so
61 The Filesystem context
64 The creation and reconfiguration of a superblock is governed by a filesystem
93      These are operations that can be done on a filesystem context (see
101      A pointer to the file_system_type of the filesystem that is being
108      A pointer to the file system's private data.  This is where the filesystem
126      replaced by the filesystem to reflect other sources, such as the parent
147      qualify it (used by FUSE).  This is available for the filesystem to set if
194 VFS, security and filesystem mount options are set individually with
198 When mounting, the filesystem is allowed to take data from any of the pointers
202 The filesystem is also allowed to allocate resources and pin them with the
207 The Filesystem Context Operations
210 The filesystem context points to a table of operations::
223 manage the filesystem context.  They are as follows:
229      Called to clean up the filesystem-specific part of the filesystem context
237      Called when a filesystem context has been duplicated to duplicate the
238      filesystem-private data.  An error may be returned to indicate failure to
245 	 filesystem-private data safe for ->free().
252      Called when a parameter is being added to the filesystem context.  param
272      If the filesystem (e.g. NFS) needs to examine the data first and then
281      information stored in the filesystem context (reconfiguration goes via a
283      filesystem context and transfer them to the superblock it creates.
296      in the filesystem context.  It may detach any resources it desires from
297      the filesystem context and transfer them to the superblock.  The
306 Filesystem context Security
309 The filesystem context contains a security pointer that the LSMs can use for
334      any resources needed.  The original filesystem context is pointed to by
353      the parameter should be passed on to the filesystem, 1 to indicate that
359      returned to prevent it being passed to the filesystem.
400 VFS Filesystem context API
403 There are four operations for creating a filesystem context and one for
411      Allocate a filesystem context for the purpose of setting up a new mount,
414      fs_type->init_fs_context() to initialise the filesystem private data.
416      fs_type specifies the filesystem type that will manage the context and
426      Allocate a filesystem context for the purpose of reconfiguring an
437      Allocate a filesystem context for the purpose of creating a new mount for
439      filesystem type that will manage the context and the reference dentry
444      filesystem type as fs_type.
450      Duplicate a filesystem context, copying any options noted and duplicating
452      for use where a filesystem has to get a mount within a mount, such as NFS4
462      Destroy a filesystem context, releasing any resources it holds.  This
464      created a filesystem context.
468         filesystem contexts are not refcounted, so this causes unconditional
482      Supply a single mount parameter to the filesystem context.  This includes
484      parameter (which may be specified multiple times if the filesystem
491      filesystem.
530      the filesystem context to select/configure the superblock.  This invokes
537      Create a mount given the parameters in the specified filesystem context.
745 A number of helper functions are provided to help a filesystem or an LSM