Lines Matching full:component

51 component, but that isn't always accurate: a pathname can lack both
59 These paths can be divided into two sections: the final component and
64 The final component is not so simple.  Not only do different system
67 pathname that is just slashes have a final component.  If it does
74 tempting to consider that to have an empty final component.  In many
77 by the final component, and they are required to work with pathnames
82   be resolved successfully unless the last pathname component before
89 "everything else" quite separately from the final component, and
109 "dentry") contains three significant fields: a component name, a
265 Secondly, when pathname lookup reaches the final component, it will
387 that is the "next" component in the pathname.
410 component is being handled, since "``..``" from the root must always stay
420 except the final component as:
424    over one component while updating ``last_type`` and ``last``.  If that
425    was the final component, then return, otherwise call
428 ``walk_component()`` is even easier.  If the component is ``LAST_DOTS``,
430 described.  If it finds a ``LAST_NORM`` component it first calls
450 Handling the final component
454 ``nd->last_type`` to refer to the final component of the path.  It does
456 component remains for the caller to sort out. Those callers are
463 directory and final component to the caller.  The caller will be either
471 calls ``walk_component()`` on the final component through a call to
490 the possibility that the final component is not ``LAST_NORM``.  If the
496 the final component, it must be a trailing slash.
826 the final component, or the very end of the path, depending on which
867 besides the already-mentioned component-name comparison, where the
928 symlinks and lead to the special care needed for the final component.
936 appear in a path prior to the final component: directories and symlinks.
939 component on the path.  Handling symbolic links requires a bit more
943 a component name refers to a symbolic link, then that component is
1118 the last component of a symlink itself points to a symlink, we
1126 old symlink as it walks that last component.  So it is quite
1137 Symlinks with no final component
1165 returns ``NULL``.  Again there is no final component and ``get_link()``
1169 Following the symlink in the final component
1172 All this leads to ``link_path_walk()`` walking down every component, and
1174 component.  This is just returned in the ``last`` field of ``nameidata``.
1178 apply special handling to the last component of that symlink, rather
1179 than just the last component of the original file name.  These callers
1186 handles the final component.  If the final component is a symlink
1189 again.  This could loop as many as 40 times if the last component of
1192 The various functions that examine the final component and possibly
1221 3. An open with O_CREAT **does** follow a symlink in the final component,
1289 component, others reflect the current state of the pathname lookup.
1302 ``LOOKUP_PARENT`` indicates that the final component hasn't been reached
1318 final component or, when creating, unlinking, or renaming, at the penultimate component.
1320 Final-component flags
1323 Some of these flags are only set when the final component is being
1325 component.
1327 ``LOOKUP_AUTOMOUNT`` ensures that, if the final component is an automount
1340 ``LOOKUP_DIRECTORY`` insists that the final component is a directory.
1341 Various callers set this and it is also set when the final component