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
466 Handling the final component
470 ``nd->last_type`` to refer to the final component of the path.  It does
472 component remains for the caller to sort out. Those callers are
479 directory and final component to the caller.  The caller will be either
487 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.
842 the final component, or the very end of the path, depending on which
883 besides the already-mentioned component-name comparison, where the
944 symlinks and lead to the special care needed for the final component.
952 appear in a path prior to the final component: directories and symlinks.
955 component on the path.  Handling symbolic links requires a bit more
959 a component name refers to a symbolic link, then that component is
1134 the last component of a symlink itself points to a symlink, we
1142 old symlink as it walks that last component.  So it is quite
1153 Symlinks with no final component
1181 returns ``NULL``.  Again there is no final component and ``get_link()``
1185 Following the symlink in the final component
1188 All this leads to ``link_path_walk()`` walking down every component, and
1190 component.  This is just returned in the ``last`` field of ``nameidata``.
1194 apply special handling to the last component of that symlink, rather
1195 than just the last component of the original file name.  These callers
1202 handles the final component.  If the final component is a symlink
1205 again.  This could loop as many as 40 times if the last component of
1208 The various functions that examine the final component and possibly
1237 3. An open with O_CREAT **does** follow a symlink in the final component,
1305 component, others reflect the current state of the pathname lookup, and some
1320 ``LOOKUP_PARENT`` indicates that the final component hasn't been reached
1336 final component or, when creating, unlinking, or renaming, at the penultimate component.
1373 Final-component flags
1376 Some of these flags are only set when the final component is being
1378 component.
1380 ``LOOKUP_AUTOMOUNT`` ensures that, if the final component is an automount
1393 ``LOOKUP_DIRECTORY`` insists that the final component is a directory.
1394 Various callers set this and it is also set when the final component