This is an automated email from the ASF dual-hosted git repository. acassis pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/nuttx.git
commit 6c272124d90554f7839e92494c137dfadd38768f Author: Marco Casaroli <[email protected]> AuthorDate: Sat Oct 17 20:23:14 2026 +0200 Documentation/v9fs: Describe symbolic links. V9FS follows symbolic links and supports readlink(), lstat(), symlink() and link() with CONFIG_FS_LINKS. The V9FS page did not describe links. Add a section about symbolic links: the option, the supported calls, the loop limit, O_NOFOLLOW and the absolute targets that are not followed. Assisted-by: Claude Code:claude-opus-5-5 Signed-off-by: Marco Casaroli <[email protected]> --- Documentation/os/filesystem/v9fs.rst | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/Documentation/os/filesystem/v9fs.rst b/Documentation/os/filesystem/v9fs.rst index f86ad98e5e5..0580518dd12 100644 --- a/Documentation/os/filesystem/v9fs.rst +++ b/Documentation/os/filesystem/v9fs.rst @@ -15,6 +15,17 @@ driver. The two currently available are: - **VIRTIO** -> ``CONFIG_V9FS_VIRTIO_9P=y`` - **SOCKET** -> ``CONFIG_V9FS_SOCKET_9P=y`` +Symbolic Links +============== + +With ``CONFIG_FS_LINKS``, V9FS follows the symbolic links on the server, +and supports ``readlink()``, ``lstat()``, ``symlink()`` and ``link()``. A +path follows at most ``SYMLOOP_MAX`` links, and a loop fails with +``ELOOP``. ``open()`` with ``O_NOFOLLOW`` does not follow a link in the +last component of the path. ``rm`` of a link removes the link, not its +target. A link with an absolute target is not followed and fails with +``ENOTSUP``, because the target is a path on the server. + NFS Mount Command =================
