From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Phillip Wood via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Phillip Wood <phillip.wood@dunelm.org.uk>
Subject: Re: [PATCH 1/2] sequencer: stop exporting GIT_REFLOG_ACTION
Date: Mon, 07 Nov 2022 17:12:08 +0100 [thread overview]
Message-ID: <221107.86iljqvhzf.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <e9c3f5ac5c6b7a01ee9e43730889d8066a270271.1667575142.git.gitgitgadget@gmail.com>
On Fri, Nov 04 2022, Phillip Wood via GitGitGadget wrote:
> From: Phillip Wood <phillip.wood@dunelm.org.uk>
> +static const char *sequencer_reflog_action(struct replay_opts *opts)
> +{
> + if (!opts->reflog_action) {
> + opts->reflog_action = getenv(GIT_REFLOG_ACTION);
> + opts->reflog_action =
> + xstrdup(opts->reflog_action ? opts->reflog_action
> + : action_name(opts));
> + }
> +
> + return opts->reflog_action;
> +}
We always return an xstrdup'd here, so this should be a "char *" return
value, not a "const char *"., but
> __attribute__((format (printf, 3, 4)))
> static const char *reflog_message(struct replay_opts *opts,
> const char *sub_action, const char *fmt, ...)
> {
> va_list ap;
> static struct strbuf buf = STRBUF_INIT;
> - char *reflog_action = getenv(GIT_REFLOG_ACTION);
>
> va_start(ap, fmt);
> strbuf_reset(&buf);
Here we just reset the strbuf...
> - strbuf_addstr(&buf, reflog_action ? reflog_action : action_name(opts));
> + strbuf_addstr(&buf, sequencer_reflog_action(opts));
Here we leak the freshly xstrdup'd value, mostly untested, but shouldn't
this instead be:
diff --git a/sequencer.c b/sequencer.c
index e23f6f0b718..58a97e04c67 100644
--- a/sequencer.c
+++ b/sequencer.c
@@ -3695,10 +3695,11 @@ static const char *reflog_message(struct replay_opts *opts,
{
va_list ap;
static struct strbuf buf = STRBUF_INIT;
+ char *msg = sequencer_reflog_action(opts);
va_start(ap, fmt);
strbuf_reset(&buf);
- strbuf_addstr(&buf, sequencer_reflog_action(opts));
+ strbuf_attach(&buf, msg, strlen(msg), strlen(msg) + 1);
if (sub_action)
strbuf_addf(&buf, " (%s)", sub_action);
if (fmt) {
Of course that requires dropping the "const", per the above...
> if (sub_action)
> strbuf_addf(&buf, " (%s)", sub_action);
> if (fmt) {
> @@ -4497,7 +4511,7 @@ static int checkout_onto(struct repository *r, struct replay_opts *opts,
> RESET_HEAD_RUN_POST_CHECKOUT_HOOK,
> .head_msg = reflog_message(opts, "start", "checkout %s",
> onto_name),
> - .default_reflog_action = "rebase"
> + .default_reflog_action = sequencer_reflog_action(opts)
Here we'd before hand a fixed string to reset_head(), but now it's
xstrdup()'d, but the corresponding free() on that side is missing.
But aren't we always just returing "rebase" here still?
> [...]
> @@ -5116,7 +5121,7 @@ static int single_pick(struct repository *r,
> TODO_PICK : TODO_REVERT;
> item.commit = cmit;
>
> - setenv(GIT_REFLOG_ACTION, action_name(opts), 0);
> + opts->reflog_message = sequencer_reflog_action(opts);
> return do_pick_commit(r, &item, opts, 0, &check_todo);
Here you're adding a new memory leak, which you can see if you run
e.g. the 1st test of ./t1013-read-tree-submodule.sh before & after this
change.
next prev parent reply other threads:[~2022-11-07 16:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 15:19 [PATCH 0/2] rebase: stop setting GIT_REFLOG_ACTION Phillip Wood via GitGitGadget
2022-11-04 15:19 ` [PATCH 1/2] sequencer: stop exporting GIT_REFLOG_ACTION Phillip Wood via GitGitGadget
2022-11-04 21:56 ` Taylor Blau
2022-11-07 16:12 ` Ævar Arnfjörð Bjarmason [this message]
2022-11-07 19:35 ` Phillip Wood
2022-11-08 9:54 ` Phillip Wood
2022-11-08 14:51 ` Ævar Arnfjörð Bjarmason
2022-11-04 15:19 ` [PATCH 2/2] rebase: " Phillip Wood via GitGitGadget
2022-11-04 21:49 ` [PATCH 0/2] rebase: stop setting GIT_REFLOG_ACTION Taylor Blau
2022-11-04 21:49 ` Taylor Blau
2022-11-07 15:51 ` Ævar Arnfjörð Bjarmason
2022-11-07 19:56 ` Taylor Blau
2022-11-09 14:21 ` [PATCH v2 " Phillip Wood via GitGitGadget
2022-11-09 14:21 ` [PATCH v2 1/2] sequencer: stop exporting GIT_REFLOG_ACTION Phillip Wood via GitGitGadget
2022-11-09 14:21 ` [PATCH v2 2/2] rebase: " Phillip Wood via GitGitGadget
2022-11-09 16:05 ` [PATCH v2 0/2] rebase: stop setting GIT_REFLOG_ACTION Ævar Arnfjörð Bjarmason
2022-11-09 16:30 ` Phillip Wood
2022-11-09 23:17 ` Taylor Blau
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=221107.86iljqvhzf.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).