Lines Matching full:component

52 component, but that isn't always accurate: a pathname can lack both
60 These paths can be divided into two sections: the final component and
65 The final component is not so simple.  Not only do different system
68 pathname that is just slashes have a final component.  If it does
75 tempting to consider that to have an empty final component.  In many
78 by the final component, and they are required to work with pathnames
83   be resolved successfully unless the last pathname component before
90 "everything else" quite separately from the final component, and
110 "dentry") contains three significant fields: a component name, a
273 Secondly, when pathname lookup reaches the final component, it will
402 that is the "next" component in the pathname.
426 component is being handled, since "``..``" from the root must always stay
436 except the final component as:
440    over one component while updating ``last_type`` and ``last``.  If that
441    was the final component, then return, otherwise call
444 ``walk_component()`` is even easier.  If the component is ``LAST_DOTS``,
446 described.  If it finds a ``LAST_NORM`` component it first calls
468 Handling the final component
472 ``nd->last_type`` to refer to the final component of the path.  It does
474 component remains for the caller to sort out. Those callers are
481 directory and final component to the caller.  The caller will be either
489 calls ``walk_component()`` on the final component through a call to
506 the possibility that the final component is not ``LAST_NORM``.  If the
512 the final component, it must be a trailing slash.
841 the final component, or the very end of the path, depending on which
882 besides the already-mentioned component-name comparison, where the
943 symlinks and lead to the special care needed for the final component.
951 appear in a path prior to the final component: directories and symlinks.
954 component on the path.  Handling symbolic links requires a bit more
958 a component name refers to a symbolic link, then that component is
1115 the last component of a symlink itself points to a symlink, we
1123 old symlink as it walks that last component.  So it is quite
1130 component of the lookup, so we will check userspace flag ``LOOKUP_FOLLOW`` to
1134 Symlinks with no final component
1162 returns ``NULL``.  Again there is no final component and pick_link()
1165 Following the symlink in the final component
1168 All this leads to ``link_path_walk()`` walking down every component, and
1170 component.  This is just returned in the ``last`` field of ``nameidata``.
1174 apply special handling to the last component of that symlink, rather
1175 than just the last component of the original file name.  These callers
1182 and then handles the final component by calling open_last_lookups() or
1187 component of each symlink is another symlink.
1189 Of the various functions that examine the final component, 
1213 3. An open with O_CREAT **does** follow a symlink in the final component,
1281 component, others reflect the current state of the pathname lookup, and some
1296 ``LOOKUP_PARENT`` indicates that the final component hasn't been reached
1312 final component or, when creating, unlinking, or renaming, at the penultimate component.
1349 Final-component flags
1352 Some of these flags are only set when the final component is being
1354 component.
1356 ``LOOKUP_AUTOMOUNT`` ensures that, if the final component is an automount
1369 ``LOOKUP_DIRECTORY`` insists that the final component is a directory.
1370 Various callers set this and it is also set when the final component