[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87v98j126r.fsf@notabene.neil.brown.name>
Date: Mon, 19 Apr 2021 11:41:00 +1000
From: NeilBrown <neilb@...e.de>
To: Fox Chen <foxhlchen@...il.com>
Cc: Fox Chen <foxhlchen@...il.com>, corbet@....net,
vegard.nossum@...cle.com, viro@...iv.linux.org.uk,
rdunlap@...radead.org, grandmaster@...klimov.de,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
gregkh@...uxfoundation.org
Subject: Re: [PATCH v2 09/12] docs: path-lookup: no get_link()
On Tue, Mar 16 2021, Fox Chen wrote:
> no get_link() anymore. we have step_into() and pick_link().
>
> walk_component() will call step_into(), in turn call pick_link,
> and return symlink name.
>
> Signed-off-by: Fox Chen <foxhlchen@...il.com>
> ---
> Documentation/filesystems/path-lookup.rst | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/filesystems/path-lookup.rst b/Documentation/filesystems/path-lookup.rst
> index 8ab95dd9046e..0d41c61f7e4f 100644
> --- a/Documentation/filesystems/path-lookup.rst
> +++ b/Documentation/filesystems/path-lookup.rst
> @@ -1103,12 +1103,10 @@ doesn't need to notice. Getting this ``name`` variable on and off the
> stack is very straightforward; pushing and popping the references is
> a little more complex.
>
> -When a symlink is found, ``walk_component()`` returns the value ``1``
> -(``0`` is returned for any other sort of success, and a negative number
> -is, as usual, an error indicator). This causes ``get_link()`` to be
> -called; it then gets the link from the filesystem. Providing that
> -operation is successful, the old path ``name`` is placed on the stack,
> -and the new value is used as the ``name`` for a while. When the end of
> +When a symlink is found, ``walk_component()`` calls ``pick_link()``,
walk_component() calls pick_link() via step_into()
??
> +it then gets the link from the filesystem returning new path ``name``.
"which returns the link from the filesystem."
With those changes (assuming you agree with them)
Reviewed-by: NeilBrown <neilb@...e.de>
Thanks,
NeilBrown
> +Providing that operation is successful, the old path ``name`` is placed on the
> +stack, and the new value is used as the ``name`` for a while. When the end of
> the path is found (i.e. ``*name`` is ``'\0'``) the old ``name`` is restored
> off the stack and path walking continues.
>
> --
> 2.30.2
Download attachment "signature.asc" of type "application/pgp-signature" (854 bytes)
Powered by blists - more mailing lists