From: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
To: git@vger.kernel.org
Cc: "Stefan Beller" <sbeller@google.com>,
"Junio C Hamano" <gitster@pobox.com>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: [PATCH] repository: fix free problem with repo_clear(the_repository)
Date: Wed, 9 May 2018 19:04:09 +0200 [thread overview]
Message-ID: <20180509170409.13666-1-pclouds@gmail.com> (raw)
the_repository is special. One of the special things about it is that
it does not allocate a new index_state object like submodules but
points to the global the_index variable instead. As a global variable,
the_index cannot be free()'d.
Add an exception for this in repo_clear(). In the future perhaps we
would be able to allocate the_repository's index on heap too. Then we
can remove revert this.
Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
---
I was trying to test the new parsed_object_pool_clear() and found this.
repository.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/repository.c b/repository.c
index a4848c1bd0..f44733524a 100644
--- a/repository.c
+++ b/repository.c
@@ -238,7 +238,9 @@ void repo_clear(struct repository *repo)
if (repo->index) {
discard_index(repo->index);
- FREE_AND_NULL(repo->index);
+ if (repo->index != &the_index)
+ free(repo->index);
+ repo->index = NULL;
}
}
--
2.17.0.705.g3525833791
next reply other threads:[~2018-05-09 17:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 17:04 Nguyễn Thái Ngọc Duy [this message]
2018-05-09 17:17 ` [PATCH] repository: fix free problem with repo_clear(the_repository) Brandon Williams
2018-05-09 17:42 ` Elijah Newren
2018-05-09 17:54 ` Duy Nguyen
2018-05-09 17:50 ` Stefan Beller
2018-05-09 18:00 ` Duy Nguyen
2018-05-09 18:09 ` Stefan Beller
2018-05-10 6:18 ` Duy Nguyen
2018-05-10 9:27 ` Junio C Hamano
2018-05-10 16:34 ` Stefan Beller
2018-05-10 6:13 ` [PATCH v2] " Nguyễn Thái Ngọc Duy
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180509170409.13666-1-pclouds@gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sbeller@google.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).