From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] delta-islands: fix segfault when freeing island marks
Date: Mon, 20 Feb 2023 08:34:45 +0100 [thread overview]
Message-ID: <Y/MilQXhFTcoefyT@ncase> (raw)
In-Reply-To: <xmqqbkltqykk.fsf@gitster.g>
[-- Attachment #1: Type: text/plain, Size: 2313 bytes --]
On Thu, Feb 16, 2023 at 10:01:31AM -0800, Junio C Hamano wrote:
> Patrick Steinhardt <ps@pks.im> writes:
>
> > In 647982bb71 (delta-islands: free island_marks and bitmaps, 2023-02-03)
> > we have introduced logic to free `island_marks` in order to reduce heap
> > memory usage in git-pack-objects(1). This commit is causing segfaults in
> > the case where this Git command does not load delta islands at all, e.g.
> > when reading object IDs from standard input. One such crash can be hit
> > when using repacking multi-pack-indices with delta islands enabled.
> >
> > The root cause of this bug is that we unconditionally dereference the
> > `island_marks` variable even in the case where it is a `NULL` pointer,
> > which is fixed by making it conditional. Note that we still leave the
> > logic in place to set the pointer to `-1` to detect use-after-free bugs
> > even when there are no loaded island marks at all.
>
> There still are unprotected uses of island_marks in delta-islands.c
> after this patch, but I think they are safe.
>
> * The callchain deduplicate_islands() -> mark_remote_island_1() ->
> create_or_get_island_marks() assume island_marks is not NULL, and
> the only caller of deduplicate_islands(), load_delta_islands(),
> initializes island_marks() before calling into it.
>
> * set_island_marks() assumes island_marks is not NULL. One of its
> two callers, resolve_tree_islands() ensures island_marks is not
> NULL before proceeding. The other one, propagate_island_marks(),
> also assumes island_marks is not NULL, and is called only from
> pack-objects.c::show_commit() when use_delta_islands is set. It
> is not apparent if island_marks has already populated when this
> happens, though.
>
> I think early in the pack-objects process, prepare_pack() calls
> resolve_tree_islands() but as we have seen, it just punts when
> island_marks is NULL, and not populates. But get_object_list()
> explicitly calls load_delta_islands() when use_delta_islands is
> set, and that happens way before prepare_pack() gets called, so we
> should be safe.
>
> Thanks.
Agreed. I also had a look at the other usages of `island_marks` and
couldn't find any obvious way to access it without it being initialized.
Patrick
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-02-20 7:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 10:29 [PATCH] delta-islands: fix segfault when freeing island marks Patrick Steinhardt
2023-02-16 12:08 ` Eric Wong
2023-02-16 17:36 ` Junio C Hamano
2023-02-20 7:38 ` Patrick Steinhardt
2023-02-21 17:15 ` Junio C Hamano
2023-02-16 18:01 ` Junio C Hamano
2023-02-20 7:34 ` Patrick Steinhardt [this message]
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=Y/MilQXhFTcoefyT@ncase \
--to=ps@pks.im \
--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).