From: "Adam Johnson via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: ZheNing Hu <adlternative@gmail.com>,
Junio C Hamano <gitster@pobox.com>, Adam Johnson <me@adamj.eu>,
Adam Johnson <me@adamj.eu>
Subject: [PATCH] ls-files: fix "--format" output of relative paths
Date: Fri, 10 Mar 2023 13:04:33 +0000 [thread overview]
Message-ID: <pull.1465.git.git.1678453473484.gitgitgadget@gmail.com> (raw)
From: Adam Johnson <me@adamj.eu>
Fix a bug introduced with the "--format" option in
ce74de931d, where relative paths were computed
using the output buffer, which could lead to
random data in the output.
Signed-off-by: Adam Johnson <me@adamj.eu>
---
ls-files: fix "--format" output of relative paths
ce74de931d introduced with the "--format" option to ls-files. This
commit had a bug: using --format='%(path)' with the "top" pathspec from
within a subdirectory would lead to random memory being added to the
output. For example, within the Documentation/ directory in Git’s own
repository:
$ git ls-files --format='%(path)' ':/' | head -n 2
../.cirrus.yml�뻤��
../.clang-format�뻤��
This is due to reuse of a string buffer for calculating the relative
path. The attached patch fixes this by using a fresh buffer, the same
pattern used in other places where relative paths are computed.
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1465%2Fadamchainz%2Ffix-ls-files-format-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1465/adamchainz/fix-ls-files-format-v1
Pull-Request: https://github.com/git/git/pull/1465
builtin/ls-files.c | 5 ++++-
t/t3013-ls-files-format.sh | 16 ++++++++++++++++
2 files changed, 20 insertions(+), 1 deletion(-)
diff --git a/builtin/ls-files.c b/builtin/ls-files.c
index 4cf8a236483..02b9bbe7eb4 100644
--- a/builtin/ls-files.c
+++ b/builtin/ls-files.c
@@ -89,12 +89,15 @@ static void write_name(const char *name)
static void write_name_to_buf(struct strbuf *sb, const char *name)
{
- const char *rel = relative_path(name, prefix_len ? prefix : NULL, sb);
+ struct strbuf buf = STRBUF_INIT;
+ const char *rel = relative_path(name, prefix_len ? prefix : NULL, &buf);
if (line_terminator)
quote_c_style(rel, sb, NULL, 0);
else
strbuf_addstr(sb, rel);
+
+ strbuf_release(&buf);
}
static const char *get_tag(const struct cache_entry *ce, const char *tag)
diff --git a/t/t3013-ls-files-format.sh b/t/t3013-ls-files-format.sh
index efb7450bf1e..ef6fb53f7f1 100755
--- a/t/t3013-ls-files-format.sh
+++ b/t/t3013-ls-files-format.sh
@@ -54,6 +54,22 @@ test_expect_success 'git ls-files --format path v.s. -s' '
test_cmp expect actual
'
+test_expect_success 'git ls-files --format with relative path' '
+ cat >expect <<-\EOF &&
+ ../o1.txt
+ ../o2.txt
+ ../o3.txt
+ ../o4.txt
+ ../o5.txt
+ ../o6.txt
+ EOF
+ mkdir sub &&
+ cd sub &&
+ git ls-files --format="%(path)" ":/" >../actual &&
+ cd .. &&
+ test_cmp expect actual
+'
+
test_expect_success 'git ls-files --format with -m' '
echo change >o1.txt &&
cat >expect <<-\EOF &&
base-commit: 768bb238c4843bf52847773a621de4dffa6b9ab5
--
gitgitgadget
next reply other threads:[~2023-03-10 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 13:04 Adam Johnson via GitGitGadget [this message]
2023-03-10 13:40 ` [PATCH] ls-files: fix "--format" output of relative paths ZheNing Hu
2023-03-10 17:39 ` Junio C Hamano
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=pull.1465.git.git.1678453473484.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=adlternative@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@adamj.eu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.