From: "René Scharfe" <l.s.r@web.de>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>, git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: Re: [RFC PATCH 5/5] strvec API users: fix more leaks by using "STRVEC_INIT_NODUP"
Date: Sat, 17 Dec 2022 13:45:42 +0100 [thread overview]
Message-ID: <0036020f-5fe7-4ad1-a66e-26db9d851035@web.de> (raw)
In-Reply-To: <RFC-patch-5.5-81742a8a6ed-20221215T090226Z-avarab@gmail.com>
Am 15.12.22 um 10:11 schrieb Ævar Arnfjörð Bjarmason:
> For these cases where most of the the strings we were pushing to the
> "struct strvec" were fixed strings, but others are dynamically
> allocated. For the latter we keep around a "to_free" list of them.
>
> Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
> ---
> builtin/describe.c | 22 +++++++++++++++++-----
> builtin/upload-archive.c | 9 +++++++--
> t/t5003-archive-zip.sh | 1 +
> 3 files changed, 25 insertions(+), 7 deletions(-)
>
> diff --git a/builtin/describe.c b/builtin/describe.c
> index cb205f6b561..eda59ebb19a 100644
> --- a/builtin/describe.c
> +++ b/builtin/describe.c
> @@ -596,8 +596,10 @@ int cmd_describe(int argc, const char **argv, const char *prefix)
> die(_("options '%s' and '%s' cannot be used together"), "--long", "--abbrev=0");
>
> if (contains) {
> + struct string_list to_free = STRING_LIST_INIT_DUP;
> struct string_list_item *item;
> - struct strvec args = STRVEC_INIT;
> + struct strvec args = STRVEC_INIT_NODUP;
> +
> int ret;
>
> strvec_pushl(&args, "name-rev",
> @@ -607,10 +609,19 @@ int cmd_describe(int argc, const char **argv, const char *prefix)
> strvec_push(&args, "--always");
> if (!all) {
> strvec_push(&args, "--tags");
> - for_each_string_list_item(item, &patterns)
> - strvec_pushf(&args, "--refs=refs/tags/%s", item->string);
> - for_each_string_list_item(item, &exclude_patterns)
> - strvec_pushf(&args, "--exclude=refs/tags/%s", item->string);
> + for_each_string_list_item(item, &patterns) {
> + char *str = xstrfmt("--refs=refs/tags/%s", item->string);
> + const char *item = string_list_append_nodup(&to_free, str)->string;
> +
> + strvec_push(&args, item);
> + }
> + for_each_string_list_item(item, &exclude_patterns) {
> + char *str = xstrfmt("--exclude=refs/tags/%s", item->string);
> +
> + const char *item = string_list_append_nodup(&to_free, str)->string;
> +
> + strvec_push(&args, item);
> + }
Having to track allocations separately for each option is tedious, as
we see here.
> }
> if (argc)
> strvec_pushv(&args, argv);
> @@ -618,6 +629,7 @@ int cmd_describe(int argc, const char **argv, const char *prefix)
> strvec_push(&args, "HEAD");
> ret = cmd_name_rev(args.nr, args.v, prefix);
> strvec_clear(&args);
> + string_list_clear(&to_free, 0);
> return ret;
> }
>
> diff --git a/builtin/upload-archive.c b/builtin/upload-archive.c
> index 6ef0d06ee8b..95c6cdc4be0 100644
> --- a/builtin/upload-archive.c
> +++ b/builtin/upload-archive.c
> @@ -19,7 +19,8 @@ static const char deadchild[] =
>
> int cmd_upload_archive_writer(int argc, const char **argv, const char *prefix)
> {
> - struct strvec sent_argv = STRVEC_INIT;
> + struct string_list to_free = STRING_LIST_INIT_DUP;
> + struct strvec sent_argv = STRVEC_INIT_NODUP;
> const char *arg_cmd = "argument ";
> int ret;
>
> @@ -34,6 +35,7 @@ int cmd_upload_archive_writer(int argc, const char **argv, const char *prefix)
> /* put received options in sent_argv[] */
> strvec_push(&sent_argv, "git-upload-archive");
> for (;;) {
> + struct string_list_item *item;
> char *buf = packet_read_line(0, NULL);
> if (!buf)
> break; /* got a flush */
> @@ -42,13 +44,16 @@ int cmd_upload_archive_writer(int argc, const char **argv, const char *prefix)
>
> if (!starts_with(buf, arg_cmd))
> die("'argument' token or flush expected");
> - strvec_push(&sent_argv, buf + strlen(arg_cmd));
> +
> + item = string_list_append(&to_free, buf + strlen(arg_cmd));
> + strvec_push(&sent_argv, item->string);
> }
>
> /* parse all options sent by the client */
> ret = write_archive(sent_argv.nr, sent_argv.v, prefix,
> the_repository, NULL, 1);
> strvec_clear(&sent_argv);
> + string_list_clear(&to_free, 0);
> return ret;
> }
>
> diff --git a/t/t5003-archive-zip.sh b/t/t5003-archive-zip.sh
> index fc499cdff01..cc1ce060558 100755
> --- a/t/t5003-archive-zip.sh
> +++ b/t/t5003-archive-zip.sh
> @@ -2,6 +2,7 @@
>
> test_description='git archive --format=zip test'
>
> +TEST_PASSES_SANITIZE_LEAK=true
> TEST_CREATE_REPO_NO_TEMPLATE=1
> . ./test-lib.sh
>
next prev parent reply other threads:[~2022-12-17 12:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 6:47 [PATCH] am: don't pass strvec to apply_parse_options() René Scharfe
2022-12-13 8:37 ` Ævar Arnfjörð Bjarmason
2022-12-13 18:31 ` René Scharfe
2022-12-14 8:44 ` Ævar Arnfjörð Bjarmason
2022-12-15 9:11 ` [RFC PATCH 0/5] strvec: add a "nodup" mode, fix memory leaks Ævar Arnfjörð Bjarmason
2022-12-15 9:11 ` [RFC PATCH 1/5] builtin/annotate.c: simplify for strvec API Ævar Arnfjörð Bjarmason
2022-12-17 12:45 ` René Scharfe
2022-12-15 9:11 ` [RFC PATCH 2/5] various: add missing strvec_clear() Ævar Arnfjörð Bjarmason
2022-12-15 9:11 ` [RFC PATCH 3/5] strvec API: add a "STRVEC_INIT_NODUP" Ævar Arnfjörð Bjarmason
2022-12-17 12:45 ` René Scharfe
2022-12-15 9:11 ` [RFC PATCH 4/5] strvec API users: fix leaks by using "STRVEC_INIT_NODUP" Ævar Arnfjörð Bjarmason
2022-12-17 12:45 ` René Scharfe
2022-12-15 9:11 ` [RFC PATCH 5/5] strvec API users: fix more " Ævar Arnfjörð Bjarmason
2022-12-17 12:45 ` René Scharfe [this message]
2022-12-17 12:45 ` [RFC PATCH 0/5] strvec: add a "nodup" mode, fix memory leaks René Scharfe
2022-12-17 13:13 ` Jeff King
2022-12-19 9:20 ` Ævar Arnfjörð Bjarmason
2023-01-07 13:21 ` Jeff King
2022-12-17 12:46 ` [PATCH] am: don't pass strvec to apply_parse_options() René Scharfe
2022-12-17 13:24 ` Jeff King
2022-12-17 16:07 ` René Scharfe
2022-12-17 21:53 ` Jeff King
2022-12-18 2:42 ` Junio C Hamano
2022-12-20 1:29 ` 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=0036020f-5fe7-4ad1-a66e-26db9d851035@web.de \
--to=l.s.r@web.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).