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 bf029a2ef5dcadb0f9e2a0edf0b6219b2d3727ce Author: Marco Casaroli <[email protected]> AuthorDate: Wed Nov 4 15:10:52 2026 +0100 Documentation/filesystem: Name CONFIG_BINFMT_BUILTIN_STRICT_PATH in binfs. Say how exec() matches a path to a builtin application, and what the option changes. Assisted-by: Claude Code:claude-opus-5-5 Signed-off-by: Marco Casaroli <[email protected]> --- Documentation/os/filesystem/binfs.rst | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/Documentation/os/filesystem/binfs.rst b/Documentation/os/filesystem/binfs.rst index c3abf1dd6ad..e5adb9a5dba 100644 --- a/Documentation/os/filesystem/binfs.rst +++ b/Documentation/os/filesystem/binfs.rst @@ -28,3 +28,10 @@ Example:: nsh> /bin/hello Hello, World!! +By default, ``exec()`` and ``posix_spawn()`` look up only the last part of a +path in the builtin applications: ``/nonexistent/hello`` also starts ``hello``. +With ``CONFIG_BINFMT_BUILTIN_STRICT_PATH``, a name with a ``/`` starts a builtin +application only if it names a file in a mounted binfs. A bare name still +starts it. The option breaks code that uses a path with no file there, such as +``/bin/sh`` with no binfs at ``/bin``: see its help text. +
