[PATCH v3 06/27] bisect: fix leaking commit list items in `check_merge_base()`
- From
Patrick Steinhardt <ps@pks.im>
- Date
- Nov 20, 2024, 13:39 UTC
- Message-ID
- <20241120-b4-pks-leak-fixes-pt10-v3-6-d67f08f45c74@pks.im>
- In-Reply-To
- <20241120-b4-pks-leak-fixes-pt10-v3-0-d67f08f45c74@pks.im>
While we free the result commit list at the end of `check_merge_base()`, we forget to free any items that we have already iterated over. Fix this by using a separate variable to iterate through them.
This leak is exposed by t6030, but plugging it does not make the whole test suite pass.
Signed-off-by: Patrick Steinhardt <ps@pks.im> --- bisect.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/bisect.c b/bisect.c index 04e9a63f11c7fa1a9dd11d3f193c500a4cb937c6..12efcff2e3c1836ab6e63d36e4d42269fbcaeaab 100644 --- a/bisect.c +++ b/bisect.c @@ -851,8 +851,8 @@ static enum bisect_error check_merge_bases(int rev_nr, struct commit **rev, int rev + 1, &result) < 0) exit(128); - for (; result; result = result->next) { - const struct object_id *mb = &result->item->object.oid; + for (struct commit_list *l = result; l; l = l->next) { + const struct object_id *mb = &l->item->object.oid; if (oideq(mb, current_bad_oid)) { res = handle_bad_merge_base(); break;
-- 2.47.0.274.g962d0b743d.dirty