From: "Lidong Yan via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>, Taylor Blau <me@ttaylorr.com>,
Lidong Yan <502024330056@smail.nju.edu.cn>
Subject: [PATCH v6 0/3] pack-bitmap: fix memory leak if load_bitmap failed
Date: Tue, 01 Jul 2025 05:32:06 +0000 [thread overview]
Message-ID: <pull.1962.v6.git.git.1751347929.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.1962.v5.git.git.1748920444.gitgitgadget@gmail.com>
Since it seems this patch has been inactive for some time, I have revised
the comments according to Taylor's feedback and submitted a new version.
This patch prevents pack-bitmap.c:load_bitmap() from nulling
bitmap_git->bitmap when loading failed. Thus eliminates memory leak. This
patch also add a test case in t5310 which use clang leak sanitizer to detect
whether leak happens when loading failed.
Lidong Yan (2):
pack-bitmap: reword comments in test_bitmap_commits()
pack-bitmap: add load corrupt bitmap test
Taylor Blau (1):
pack-bitmap: fix memory leak if load_bitmap() failed
pack-bitmap.c | 88 ++++++++++++++++++++++++++++++-----------
pack-bitmap.h | 1 +
t/helper/test-bitmap.c | 8 ++++
t/t5310-pack-bitmaps.sh | 30 ++++++++++++++
4 files changed, 103 insertions(+), 24 deletions(-)
base-commit: f0135a9047ca37d4d117dcf21f7e3e89fad85d00
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1962%2Fbrandb97%2Ffix-pack-bitmap-leak-v6
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1962/brandb97/fix-pack-bitmap-leak-v6
Pull-Request: https://github.com/git/git/pull/1962
Range-diff vs v5:
1: 9ce2135df2a ! 1: 3d70e14e415 pack-bitmap: fix memory leak if load_bitmap() failed
@@ Commit message
});
, but won't since load_bitmap() already called kh_destroy_oid_map() and
- NULL'd the "bitmaps" pointer from within its "failed" label.
-
- So I think if you got part of the way through loading bitmap entries and
- then failed, you would leak all of the previous entries that you were
- able to load successfully.
+ NULL'd the "bitmaps" pointer from within its "failed" label. Thus if you
+ got part of the way through loading bitmap entries and then failed, you
+ would leak all of the previous entries that you were able to load
+ successfully.
The solution is to remove the error handling code in load_bitmap(), because
its caller will always call free_bitmap_index() in case of an error.
2: a75d0a3cc7f ! 2: 6a082930ea3 pack-bitmap: reword comments in test_bitmap_commits()
@@ Metadata
## Commit message ##
pack-bitmap: reword comments in test_bitmap_commits()
- In pack-bitmap.c:test_bitmap_commits(), it comments
-
- /*
- * As this function is only used to print bitmap selected
- * commits, we don't have to read the commit table.
- */
-
- This suggests that we can avoid reading the commit table altogether.
- However, this comment is misleading. The reason we load bitmap entries here
- is because test_bitmap_commits() needs to print the commit IDs from the
+ The comment in pack-bitmap.c:test_bitmap_commits(), suggests that
+ we can avoid reading the commit table altogether. However, this
+ comment is misleading. The reason we load bitmap entries here is
+ because test_bitmap_commits() needs to print the commit IDs from the
bitmap, and we must read the bitmap entries to obtain those commit IDs.
So reword this comment.
@@ pack-bitmap.c: int test_bitmap_commits(struct repository *r)
/*
- * As this function is only used to print bitmap selected
- * commits, we don't have to read the commit table.
-+ * Since this function needs to print bitmap selected
++ * Since this function needs to print the bitmapped
+ * commits, bypass the commit lookup table (if one exists)
+ * by forcing the bitmap to eagerly load its entries.
*/
3: 05140e2171d ! 3: c1b5d030133 pack-bitmap: add load corrupt bitmap test
@@ Metadata
## Commit message ##
pack-bitmap: add load corrupt bitmap test
- This patch add test_bitmap_list_commits_offset() in patch-bitmap.c,
- a new test helper command `test-tool bitmap list-commits-offset`,
- and a `load corrupt bitmap` test case in t5310.
-
- The `load corrupt bitmap` test case intentionally corrupt the
- "xor_offset" field of the first entry. And the newly added helper
- can help to find position of "xor_offset" in bitmap file.
+ t5310 lacks a test to ensure git works correctly when commit bitmap
+ data is corrupted. So this patch add test helper in pack-bitmap.c to
+ list each commit bitmap position in bitmap file and `load corrupt bitmap`
+ test case in t/t5310 to corrupt a commit bitmap before loading it.
Signed-off-by: Lidong Yan <502024330056@smail.nju.edu.cn>
--
gitgitgadget
next prev parent reply other threads:[~2025-07-01 5:32 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 12:22 [PATCH] pack-bitmap: fix memory leak if `load_bitmap_entries_v1` failed Lidong Yan via GitGitGadget
2025-05-12 13:13 ` Jeff King
2025-05-13 17:47 ` Taylor Blau
2025-05-14 13:18 ` Junio C Hamano
2025-05-14 18:03 ` Jeff King
2025-05-15 1:37 ` lidongyan
2025-05-20 9:23 ` [PATCH v2 0/3] pack-bitmap: fix memory leak if load_bitmap_entries_v1 failed Lidong Yan via GitGitGadget
2025-05-20 9:23 ` [PATCH v2 1/3] pack-bitmap: fix memory leak if `load_bitmap_entries_v1` failed Lidong Yan via GitGitGadget
2025-05-20 9:23 ` [PATCH v2 2/3] " Taylor Blau via GitGitGadget
2025-05-21 23:54 ` Taylor Blau
2025-05-22 15:15 ` lidongyan
2025-05-22 21:22 ` Junio C Hamano
2025-05-20 9:23 ` [PATCH v2 3/3] pack-bitmap: add loading corrupt bitmap_index test Lidong Yan via GitGitGadget
2025-05-22 0:08 ` Taylor Blau
2025-05-22 15:05 ` lidongyan
2025-05-23 0:31 ` Taylor Blau
2025-05-23 7:17 ` lidongyan
2025-05-25 2:06 ` [PATCH v3 0/2] pack-bitmap: fix memory leak if load_bitmap_entries_v1 failed Lidong Yan via GitGitGadget
2025-05-25 2:06 ` [PATCH v3 1/2] pack-bitmap: fix memory leak if `load_bitmap_entries_v1` failed Taylor Blau via GitGitGadget
2025-05-25 2:06 ` [PATCH v3 2/2] pack-bitmap: add load corrupt bitmap test Lidong Yan via GitGitGadget
2025-05-25 2:43 ` [PATCH v4 0/2] pack-bitmap: fix memory leak if load_bitmap failed Lidong Yan via GitGitGadget
2025-05-25 2:43 ` [PATCH v4 1/2] pack-bitmap: fix memory leak if load_bitmap() failed Taylor Blau via GitGitGadget
2025-05-29 15:33 ` Junio C Hamano
2025-05-29 19:57 ` Taylor Blau
2025-05-29 22:04 ` Junio C Hamano
2025-05-30 3:50 ` lidongyan
2025-05-25 2:43 ` [PATCH v4 2/2] pack-bitmap: add load corrupt bitmap test Lidong Yan via GitGitGadget
2025-05-29 15:45 ` Junio C Hamano
2025-05-29 21:21 ` Taylor Blau
2025-05-30 3:53 ` lidongyan
2025-05-29 21:20 ` Taylor Blau
2025-05-30 4:03 ` lidongyan
2025-06-03 3:14 ` [PATCH v5 0/3] pack-bitmap: fix memory leak if load_bitmap failed Lidong Yan via GitGitGadget
2025-06-03 3:14 ` [PATCH v5 1/3] pack-bitmap: fix memory leak if load_bitmap() failed Taylor Blau via GitGitGadget
2025-06-03 3:14 ` [PATCH v5 2/3] pack-bitmap: reword comments in test_bitmap_commits() Lidong Yan via GitGitGadget
2025-06-03 22:13 ` Taylor Blau
2025-06-03 3:14 ` [PATCH v5 3/3] pack-bitmap: add load corrupt bitmap test Lidong Yan via GitGitGadget
2025-06-03 22:14 ` [PATCH v5 0/3] pack-bitmap: fix memory leak if load_bitmap failed Taylor Blau
2025-07-01 5:32 ` Lidong Yan via GitGitGadget [this message]
2025-07-01 5:32 ` [PATCH v6 1/3] pack-bitmap: fix memory leak if load_bitmap() failed Taylor Blau via GitGitGadget
2025-07-01 5:32 ` [PATCH v6 2/3] pack-bitmap: reword comments in test_bitmap_commits() Lidong Yan via GitGitGadget
2025-07-01 5:32 ` [PATCH v6 3/3] pack-bitmap: add load corrupt bitmap test Lidong Yan via GitGitGadget
2025-07-07 22:53 ` [PATCH v6 0/3] pack-bitmap: fix memory leak if load_bitmap failed Junio C Hamano
2025-07-08 22:10 ` Taylor Blau
2025-07-08 22:35 ` 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=pull.1962.v6.git.git.1751347929.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=502024330056@smail.nju.edu.cn \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
/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).