Documentation/filesystems/path-lookup.rst

28 them until the final part.  Well before we get to symlinks we have
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
90 "everything else" quite separately from the final component, and
273 Secondly, when pathname lookup reaches the final component, it will
436 except the final component as:
441    was the final component, then return, otherwise call
468 Handling the final component
472 ``nd->last_type`` to refer to the final component of the path.  It does
473 not call ``walk_component()`` that last time.  Handling that final
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
490 ``lookup_last()``.  ``path_lookupat()`` returns just the final dentry.
500 or without O_EXCL), final "``/``" characters, and trailing symbolic
501 links.  We will revisit this in the final part of this series, which
506 the possibility that the final component is not ``LAST_NORM``.  If the
512 the final component, it must be a trailing slash.
663 error ``ESTALE`` a final attempt is made with ``LOOKUP_REVAL`` set (and no
841 the final component, or the very end of the path, depending on which
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.
1099 components in the path and all of the non-final symlinks.  As symlinks
1129 current symlink, and ``WALK_TRAILING`` which indicates that it is on the final
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
1169 following all symbolic links it finds, until it reaches the final
1182 and then handles the final component by calling open_last_lookups() or
1189 Of the various functions that examine the final component,
1202    the filesystem provides it) to combine the final lookup with the open, or
1213 3. An open with O_CREAT **does** follow a symlink in the final component,
1280 lookup process.  Many of these are only meaningful on the final
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
1353 considered.  Others are only checked for when considering that final
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