From: Willy Tarreau <w@1wt.eu>
To: Daniel Palmer <daniel@thingy.jp>
Cc: linux@weissschuh.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] tools/nolibc: unistd: Add getcwd()
Date: Thu, 2 Jul 2026 13:33:03 +0200 [thread overview]
Message-ID: <akZMb6lbcpxfagzg@1wt.eu> (raw)
In-Reply-To: <20260702085101.3304547-2-daniel@thingy.jp>
Hi Daniel,
On Thu, Jul 02, 2026 at 05:50:59PM +0900, Daniel Palmer wrote:
> Add getcwd() for getting the current working directory.
>
> The behaviour matches what musl is doing except for one
> important difference: If the passed buf is NULL musl (and glibc)
> uses a big buffer on the stack and that is then strdup()'d and
> returned.
>
> According to the man page for getcwd() this is a glibc extension
> and I don't think we need it in nolibc.
I entirely agree.
> Signed-off-by: Daniel Palmer <daniel@thingy.jp>
>
> ---
> tools/include/nolibc/unistd.h | 42 +++++++++++++++++++++++++++++++++++
> 1 file changed, 42 insertions(+)
>
> diff --git a/tools/include/nolibc/unistd.h b/tools/include/nolibc/unistd.h
> index 79599ceef45d..2e0edbc26315 100644
> --- a/tools/include/nolibc/unistd.h
> +++ b/tools/include/nolibc/unistd.h
> @@ -73,6 +73,48 @@ int ftruncate(int fd, off_t length)
> return __sysret(_sys_ftruncate(fd, length));
> }
>
> +/*
> + * char *getcwd(char *buf, size_t size);
> + */
> +
> +static __attribute__((unused))
> +int _sys_getcwd(char *buf, size_t size)
> +{
> + return __nolibc_syscall2(__NR_getcwd, buf, size);
> +}
> +
> +static __attribute__((unused))
> +char *getcwd(char *buf, size_t size)
> +{
> + int ret;
> +
> + /* Unlike other libc's we don't handle passing NULL for buf */
> + if (!buf || !size) {
> + SET_ERRNO(EINVAL);
> + return NULL;
> + }
> +
> + ret = __sysret(_sys_getcwd(buf, size));
> +
> + /* On error return NULL, __sysret() above will have set errno */
> + if (ret < 0)
> + return NULL;
> +
> + /* Handle no path being written or the kernel putting
> + * "(unreachable)" into the buffer instead of a path.
> + * This matches what musl is doing.
> + */
> + if (ret == 0 || buf[0] != '/') {
> + SET_ERRNO(ENOENT);
> + return NULL;
> + }
> +
> + /* ret must be the number of bytes written at this point,
> + * so return the pointer to buf.
> + */
> + return buf;
> +}
> +
> static __attribute__((unused))
> int msleep(unsigned int msecs)
> {
LGTM.
Acked-by: Willy Tarreau <w@1wt.eu>
Willy
next prev parent reply other threads:[~2026-07-02 11:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 8:50 [PATCH v3 0/3] nolibc: Add getcwd() and readlink() Daniel Palmer
2026-07-02 8:50 ` [PATCH v3 1/3] tools/nolibc: unistd: Add getcwd() Daniel Palmer
2026-07-02 11:33 ` Willy Tarreau [this message]
2026-07-02 8:51 ` [PATCH v3 2/3] tools/nolibc: unistd: Add readlink() Daniel Palmer
2026-07-02 11:34 ` Willy Tarreau
2026-07-02 8:51 ` [PATCH v3 3/3] selftests/nolibc: Add test for getcwd() and readlink() Daniel Palmer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=akZMb6lbcpxfagzg@1wt.eu \
--to=w@1wt.eu \
--cc=daniel@thingy.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox