From: Natanael Copa <ncopa@alpinelinux.org>
To: musl@lists.openwall.com
Subject: Re: [musl] [PATCH] make realpath replace leading // with a single /
Date: Wed, 13 Jan 2021 14:38:09 +0100 [thread overview]
Message-ID: <20210113143809.608ea269@ncopa-desktop.lan> (raw)
In-Reply-To: <20210113132835.22685-1-ncopa@alpinelinux.org>
On Wed, 13 Jan 2021 14:28:35 +0100
Natanael Copa <ncopa@alpinelinux.org> wrote:
> On some systems a leading double slash may have special meaning, so
> POSIX[1] says that "If a pathname begins with two successive <slash>
> characters, the first component following the leading <slash> characters
> may be interpreted in an implementation-defined manner"
>
> While current musl implementation is technically correct, most other
> systems' (at least GNU libc, freebsd, openbsd, netbsd macOS)
> implementations will replace a leading // with a single /. Make musl
> do the same to avoid surprises.
>
> [1]: https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html#tag_04_13
> ---
> src/misc/realpath.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/src/misc/realpath.c b/src/misc/realpath.c
> index db8b74dc..414b4741 100644
> --- a/src/misc/realpath.c
> +++ b/src/misc/realpath.c
> @@ -46,9 +46,6 @@ restart:
> q=0;
> output[q++] = '/';
> p++;
> - /* Initial // is special. */
> - if (stack[p] == '/' && stack[p+1] != '/')
> - output[q++] = '/';
> continue;
> }
>
This fixes gettext's (gnulib) testsuite, which tests if realpath("//",
NULL) return "/" and fails if it doesn't.
I ran this testcase on multiple systems:
#include <stdio.h>
#include <stdlib.h>
int main() {
printf("%s\n", realpath("//", NULL));
return 0;
}
musl 1.1.24: /
ubuntu 20.03: /
macOS Big Sur: /
OpenBSD 6.8: /
FreeBSD 12.2: /
NetBSD 9.1: /
musl (current) //
I don't know why this behavior was introduced in musl, but I think
this only adds meaningless friction to downstream users.
-nc
next prev parent reply other threads:[~2021-01-13 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 13:28 Natanael Copa
2021-01-13 13:38 ` Natanael Copa [this message]
2021-01-13 18:01 ` Rich Felker
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=20210113143809.608ea269@ncopa-desktop.lan \
--to=ncopa@alpinelinux.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).