From: Junio C Hamano <gitster@pobox.com>
To: Emily M Klassen <forivall@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] revision: fix missing null for freed memory
Date: Mon, 10 Feb 2025 08:02:14 -0800 [thread overview]
Message-ID: <xmqqtt91dbzt.fsf@gitster.g> (raw)
In-Reply-To: <20250208061702.88469-1-forivall@gmail.com> (Emily M. Klassen's message of "Fri, 7 Feb 2025 22:17:02 -0800")
Emily M Klassen <forivall@gmail.com> writes:
> Subject: Re: [PATCH] revision: fix missing null for freed memory
>
> "git log --graph --no-graph" missed cleaning up the output_prefix and
> output_prefix_data pointers. This resulted in a segfault when using "--patch",
> "--name-status" or "--name-only", as the output_prefix_data continued to be in
> use after free()
Rereading the title, I cannot make sense out of "fix missing null"
and guess what it wants to say. Is "null" here used as a verb to
mean "to assign a NULL to a variable that points at ..."?
revision: clear graph callback upon "--no-graph"
"git log --graph --no-graph" first populates the .output_prefix
member of diffopt, which is a callback function, to compute
"--graph" header, and then discards the data the callback needs
to compute the graph header but forgets to clear .output_prefix
pointer in response to "--no-graph". At runtime, we end up
calling the function that we should not.
Clear the member to stop making callback, and for a better
hyginene, also clear the pointer pointing at a freed memory.
or something?
Other than that, as I said earlier, the patch looks good.
Thanks.
> Signed-off-by: Emily M Klassen <forivall@gmail.com>
> ---
> I previously reported this a few hours ago, and ended up digging in and figuring
> it out. I'll make sure to bottom reply in the follow ups to this patch.
>
> revision.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/revision.c b/revision.c
> index 474fa1e767..84cb028e11 100644
> --- a/revision.c
> +++ b/revision.c
> @@ -2615,6 +2615,8 @@ static int handle_revision_opt(struct rev_info *revs, int argc, const char **arg
> graph_clear(revs->graph);
> revs->graph = graph_init(revs);
> } else if (!strcmp(arg, "--no-graph")) {
> + revs->diffopt.output_prefix = NULL;
> + revs->diffopt.output_prefix_data = NULL;
> graph_clear(revs->graph);
> revs->graph = NULL;
> } else if (!strcmp(arg, "--encode-email-headers")) {
next prev parent reply other threads:[~2025-02-10 16:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 6:17 [PATCH] revision: fix missing null for freed memory Emily M Klassen
2025-02-08 21:53 ` Junio C Hamano
2025-02-10 16:02 ` Junio C Hamano [this message]
2025-02-10 20:56 ` Emily Klassen
2025-02-13 0:42 ` Junio C Hamano
2025-02-11 7:55 ` Patrick Steinhardt
2025-02-11 19:31 ` D. Ben Knoble
2025-02-11 20:22 ` D. Ben Knoble
2025-02-11 21:29 ` Jeff King
2025-02-11 23:09 ` Junio C Hamano
2025-02-12 5:30 ` Patrick Steinhardt
2025-02-13 21:07 ` Ben Knoble
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=xmqqtt91dbzt.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=forivall@gmail.com \
--cc=git@vger.kernel.org \
/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).