From: Junio C Hamano <gitster@pobox.com>
To: Brandon Williams <bmwill@google.com>
Cc: git@vger.kernel.org, sbeller@google.com, peff@peff.net,
jacob.keller@gmail.com
Subject: Re: [PATCH] real_path: make real_path thread-safe
Date: Tue, 06 Dec 2016 15:44:17 -0800 [thread overview]
Message-ID: <xmqqtwagy65q.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <1480964316-99305-2-git-send-email-bmwill@google.com> (Brandon Williams's message of "Mon, 5 Dec 2016 10:58:36 -0800")
Brandon Williams <bmwill@google.com> writes:
> +/* removes the last path component from 'path' except if 'path' is root */
> +static void strip_last_component(struct strbuf *path)
> +{
> + if (path->len > 1) {
> + char *last_slash = find_last_dir_sep(path->buf);
> + strbuf_setlen(path, last_slash - path->buf);
> + }
> +}
You use find_last_dir_sep() which takes care of "Windows uses
backslash" issue. Is this function expected to be fed something
like "C:\My Files\foo.txt" and more importantly "C:\My Files"? Or
is that handled by a lot higher level up in the callchain? I am
reacting the comparison of path->len and 1 here.
Also is the input expected to be normalized? Are we expected to be
fed something like "/a//b/./c/../d/e" and react sensibly, or is that
handled by a lot higher level up in the callchain?
> +/* gets the next component in 'remaining' and places it in 'next' */
> +static void get_next_component(struct strbuf *next, struct strbuf *remaining)
> +{
> + char *start = NULL;
> + char *end = NULL;
> +
> + strbuf_reset(next);
> +
> + /* look for the next component */
> + /* Skip sequences of multiple path-separators */
> + for (start = remaining->buf; is_dir_sep(*start); start++)
> + /* nothing */;
Style:
; /* nothing */
> + /* Find end of the path component */
> + for (end = start; *end && !is_dir_sep(*end); end++)
> + /* nothing */;
> +
> + strbuf_add(next, start, end - start);
OK, so this was given "///foo/bar" in "remaining" and appended
'foo/' to "next". I.e. deduping of slashes is handled here.
POSIX cares about treating "//" at the very beginning of the path
specially. Is that supposed to be handled here, or by a lot higher
level up in the callchain?
> + /* remove the component from 'remaining' */
> + strbuf_remove(remaining, 0, end - remaining->buf);
> +}
> +
> /* We allow "recursive" symbolic links. Only within reason, though. */
> -#define MAXDEPTH 5
> +#define MAXSYMLINKS 5
>
> /*
> * Return the real path (i.e., absolute path, with symlinks resolved
> @@ -21,7 +51,6 @@ int is_directory(const char *path)
> * absolute_path().) The return value is a pointer to a static
> * buffer.
> *
> * The directory part of path (i.e., everything up to the last
> * dir_sep) must denote a valid, existing directory, but the last
> * component need not exist. If die_on_error is set, then die with an
> @@ -33,22 +62,16 @@ int is_directory(const char *path)
> */
> static const char *real_path_internal(const char *path, int die_on_error)
> {
> + static struct strbuf resolved = STRBUF_INIT;
This being 'static' would probably mean that this is not reentrant,
which goes against the title of the patch.
next prev parent reply other threads:[~2016-12-06 23:44 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 18:58 [PATCH] making real_path thread-safe Brandon Williams
2016-12-05 18:58 ` [PATCH] real_path: make " Brandon Williams
2016-12-05 19:57 ` Stefan Beller
2016-12-05 20:12 ` Brandon Williams
2016-12-05 20:38 ` Stefan Beller
2016-12-05 20:14 ` Stefan Beller
2016-12-05 20:16 ` Brandon Williams
2016-12-08 9:41 ` Duy Nguyen
2016-12-08 17:50 ` Brandon Williams
2016-12-06 23:44 ` Junio C Hamano [this message]
2016-12-07 0:10 ` Brandon Williams
2016-12-07 1:12 ` Ramsay Jones
2016-12-07 20:14 ` Torsten Bögershausen
2016-12-07 20:32 ` Junio C Hamano
2016-12-07 22:13 ` Brandon Williams
2016-12-08 7:55 ` Torsten Bögershausen
2016-12-08 18:41 ` Johannes Sixt
2016-12-08 19:02 ` Brandon Williams
2016-12-07 20:43 ` Johannes Sixt
2016-12-07 22:29 ` Brandon Williams
2016-12-08 11:32 ` Johannes Sixt
2016-12-08 16:54 ` Junio C Hamano
2016-12-08 23:58 ` [PATCH v2 0/4] road to reentrant real_path Brandon Williams
2016-12-08 23:58 ` [PATCH v2 1/4] real_path: resolve symlinks by hand Brandon Williams
2016-12-09 1:49 ` Jacob Keller
2016-12-09 14:33 ` Johannes Sixt
2016-12-09 20:04 ` Brandon Williams
2016-12-08 23:58 ` [PATCH v2 2/4] real_path: convert real_path_internal to strbuf_realpath Brandon Williams
2016-12-08 23:58 ` [PATCH v2 3/4] real_path: create real_pathdup Brandon Williams
2016-12-09 14:35 ` Johannes Sixt
2016-12-08 23:58 ` [PATCH v2 4/4] real_path: have callers use real_pathdup and strbuf_realpath Brandon Williams
2016-12-09 12:33 ` [PATCH v2 0/4] road to reentrant real_path Duy Nguyen
2016-12-09 19:42 ` Brandon Williams
2016-12-10 11:02 ` Duy Nguyen
2016-12-12 18:16 ` [PATCH v3 " Brandon Williams
2016-12-12 18:16 ` [PATCH v3 1/4] real_path: resolve symlinks by hand Brandon Williams
2016-12-12 22:19 ` Junio C Hamano
2016-12-12 22:50 ` Brandon Williams
2016-12-12 23:32 ` Junio C Hamano
2016-12-12 18:16 ` [PATCH v3 2/4] real_path: convert real_path_internal to strbuf_realpath Brandon Williams
2016-12-12 22:20 ` Junio C Hamano
2016-12-12 18:16 ` [PATCH v3 3/4] real_path: create real_pathdup Brandon Williams
2016-12-12 22:25 ` Junio C Hamano
2016-12-12 18:16 ` [PATCH v3 4/4] real_path: have callers use real_pathdup and strbuf_realpath Brandon Williams
2016-12-12 22:26 ` Junio C Hamano
2016-12-12 23:47 ` Junio C Hamano
2016-12-12 23:58 ` Stefan Beller
2016-12-13 1:15 ` Brandon Williams
2016-12-13 6:39 ` Junio C Hamano
2016-12-21 21:51 ` [PATCH bw/realpath-wo-chdir] real_path: canonicalize directory separators in root parts Johannes Sixt
2016-12-21 22:33 ` Brandon Williams
2016-12-22 6:07 ` Johannes Sixt
2016-12-22 17:33 ` Brandon Williams
2016-12-22 18:54 ` Johannes Sixt
2016-12-22 19:33 ` Junio C Hamano
2017-01-03 19:09 ` [PATCH v4 0/5] road to reentrant real_path Brandon Williams
2017-01-03 19:09 ` [PATCH v4 1/5] real_path: resolve symlinks by hand Brandon Williams
2017-01-03 19:09 ` [PATCH v4 2/5] real_path: convert real_path_internal to strbuf_realpath Brandon Williams
2017-01-03 19:09 ` [PATCH v4 3/5] real_path: create real_pathdup Brandon Williams
2017-01-03 19:09 ` [PATCH v4 4/5] real_path: have callers use real_pathdup and strbuf_realpath Brandon Williams
2017-01-04 1:07 ` Jacob Keller
2017-01-04 18:14 ` Brandon Williams
2017-01-03 19:09 ` [PATCH v4 5/5] real_path: canonicalize directory separators in root parts Brandon Williams
2017-01-04 0:48 ` [PATCH v4 0/5] road to reentrant real_path Jeff King
2017-01-04 6:56 ` Torsten Bögershausen
2017-01-04 7:01 ` Jeff King
2017-01-04 18:13 ` Brandon Williams
2017-01-04 18:22 ` Stefan Beller
2017-01-04 21:46 ` Jacob Keller
2017-01-04 21:55 ` Brandon Williams
2017-01-04 22:01 ` [PATCH v5 " Brandon Williams
2017-01-04 22:01 ` [PATCH v5 1/5] real_path: resolve symlinks by hand Brandon Williams
2017-01-04 22:01 ` [PATCH v5 2/5] real_path: convert real_path_internal to strbuf_realpath Brandon Williams
2017-01-04 22:01 ` [PATCH v5 3/5] real_path: create real_pathdup Brandon Williams
2017-01-04 22:01 ` [PATCH v5 4/5] real_path: have callers use real_pathdup and strbuf_realpath Brandon Williams
2017-01-04 22:01 ` [PATCH v5 5/5] real_path: canonicalize directory separators in root parts Brandon Williams
2017-01-08 3:09 ` [PATCH v5 0/5] road to reentrant real_path Junio C Hamano
2017-01-09 18:04 ` Brandon Williams
2017-01-09 18:18 ` Junio C Hamano
2017-01-09 18:24 ` Brandon Williams
2017-01-09 19:26 ` Junio C Hamano
2017-01-09 18:50 ` [PATCH 1/2] real_path: prevent redefinition of MAXSYMLINKS Brandon Williams
2017-01-09 18:50 ` [PATCH 2/2] real_path: set errno when max number of symlinks is exceeded Brandon Williams
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqtwagy65q.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=jacob.keller@gmail.com \
--cc=peff@peff.net \
--cc=sbeller@google.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://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).