real_path: remove unsafe API
Returning a shared buffer invites very subtle bugs due to reentrancy or
multi-threading, as demonstrated by the previous patch.
There was an unfinished effort to abolish this [1].
Let's finally rid of `real_path()`, using `strbuf_realpath()` instead.
This patch uses a local `strbuf` for most places where `real_path()` was
previously called.
However, two places return the value of `real_path()` to the caller. For
them, a `static` local `strbuf` was added, effectively pushing the
problem one level higher:
read_gitfile_gently()
get_superproject_working_tree()
[1] https://lore.kernel.org/git/1480964316-99305-1-git-send-email-bmwill@google.com/
Signed-off-by: Alexandr Miloslavskiy <alexandr.miloslavskiy@syntevo.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
committed by
Junio C Hamano
parent
0915a5b4cd
commit
3d7747e318
@ -290,11 +290,14 @@ int cmd__path_utils(int argc, const char **argv)
|
||||
}
|
||||
|
||||
if (argc >= 2 && !strcmp(argv[1], "real_path")) {
|
||||
struct strbuf realpath = STRBUF_INIT;
|
||||
while (argc > 2) {
|
||||
puts(real_path(argv[2]));
|
||||
strbuf_realpath(&realpath, argv[2], 1);
|
||||
puts(realpath.buf);
|
||||
argc--;
|
||||
argv++;
|
||||
}
|
||||
strbuf_release(&realpath);
|
||||
return 0;
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user