Lines Matching full:context

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.
33  (2) Parse the parameters and attach them to the context.  Parameters are
37  (3) Validate and pre-process the context.
43  (6) Return an error message attached to the context.
45  (7) Destroy the context.
53 context, including the additional space, and the second points to the
61 The Filesystem context
65 context.  This is represented by the fs_context structure::
92      These are operations that can be done on a filesystem context (see
180      This indicates the purpose for which the context is intended.  The
189 The mount context is created by calling vfs_new_fs_context() or
199 in the mount context.
202 mount context.  For instance, NFS might pin the appropriate protocol version
206 The Filesystem Context Operations
209 The filesystem context points to a table of operations::
222 manage the filesystem context.  They are as follows:
228      Called to clean up the filesystem-specific part of the filesystem context
229      when the context is destroyed.  It should be aware that parts of the
230      context may have been removed and NULL'd out by ->get_tree().
236      Called when a filesystem context has been duplicated to duplicate the
251      Called when a parameter is being added to the filesystem context.  param
253      will have been weeded out and fc->sb_flags updated in the context.
280      information stored in the filesystem context (reconfiguration goes via a
282      filesystem context and transfer them to the superblock it creates.
287      The phase on a userspace-driven context will be set to only allow this to
288      be called once on any particular context.
295      in the filesystem context.  It may detach any resources it desires from
296      the filesystem context and transfer them to the superblock.  The
305 Filesystem context Security
308 The filesystem context contains a security pointer that the LSMs can use for
309 building up a security context for the superblock to be mounted.  There are a
321      reference will be non-NULL if the context is being created for superblock
333      any resources needed.  The original filesystem context is pointed to by
384      Called to apply any reconfiguration to an LSM's context.  It must not
395      to the context is permitted to be attached to the specified mountpoint.
399 VFS Filesystem context API
402 There are four operations for creating a filesystem context and one for
403 destroying a context:
410      Allocate a filesystem context for the purpose of setting up a new mount,
415      fs_type specifies the filesystem type that will manage the context and
425      Allocate a filesystem context for the purpose of reconfiguring an
436      Allocate a filesystem context for the purpose of creating a new mount for
438      filesystem type that will manage the context and the reference dentry
449      Duplicate a filesystem context, copying any options noted and duplicating
455      The purpose in the new context is inherited from the old one.
461      Destroy a filesystem context, releasing any resources it holds.  This
463      created a filesystem context.
471 context pointer or a negative error code.
481      Supply a single mount parameter to the filesystem context.  This includes
529      the filesystem context to select/configure the superblock.  This invokes
536      Create a mount given the parameters in the specified filesystem context.