No follow_managed() anymore, handle_mounts(), traverse_mounts(), will do the job. see commit: 9deed3ebca244663530782631834e706a86a8c8f
Signed-off-by: Fox Chen <foxhlc...@gmail.com> --- Documentation/filesystems/path-lookup.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/filesystems/path-lookup.rst b/Documentation/filesystems/path-lookup.rst index c482e1619e77..e778db767120 100644 --- a/Documentation/filesystems/path-lookup.rst +++ b/Documentation/filesystems/path-lookup.rst @@ -448,8 +448,8 @@ described. If it finds a ``LAST_NORM`` component it first calls filesystem to revalidate the result if it is that sort of filesystem. If that doesn't get a good result, it calls "``lookup_slow()``" which takes ``i_rwsem``, rechecks the cache, and then asks the filesystem -to find a definitive answer. Each of these will call -``follow_managed()`` (as described below) to handle any mount points. +to find a definitive answer. In ``step_into()``, ``handle_mount()`` will be +called to handle any mount point. In the absence of symbolic links, ``walk_component()`` creates a new ``struct path`` containing a counted reference to the new dentry and a @@ -536,7 +536,7 @@ tree, but a few notes specifically related to path lookup are in order here. The Linux VFS has a concept of "managed" dentries which is reflected -in function names such as "``follow_managed()``". There are three +in function names such as "``traverse_mounts()``". There are three potentially interesting things about these dentries corresponding to three different flags that might be set in ``dentry->d_flags``: -- 2.30.0
