cache-tree: refactor verification to return error codes
The function `cache_tree_verify()` will `BUG()` whenever it finds that the cache-tree extension of the index is corrupt. The function is thus inherently untestable because the resulting call to `abort()` will be detected by our testing framework and labelled an error. And rightfully so: it shouldn't ever be possible to hit bugs, as they should indicate a programming error rather than corruption of on-disk state. Refactor the function to instead return error codes. This also ensures that the function can be used e.g. by git-fsck(1) without the whole process dying. Furthermore, this refactoring plugs some memory leaks when returning early by creating a common exit path. Signed-off-by: Patrick Steinhardt <ps@pks.im> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
committed by
Junio C Hamano
parent
3969d78396
commit
9f119599a6
@@ -2070,9 +2070,13 @@ int unpack_trees(unsigned len, struct tree_desc *t, struct unpack_trees_options
|
||||
if (o->dst_index) {
|
||||
move_index_extensions(&o->internal.result, o->src_index);
|
||||
if (!ret) {
|
||||
if (git_env_bool("GIT_TEST_CHECK_CACHE_TREE", 0))
|
||||
cache_tree_verify(the_repository,
|
||||
&o->internal.result);
|
||||
if (git_env_bool("GIT_TEST_CHECK_CACHE_TREE", 0) &&
|
||||
cache_tree_verify(the_repository,
|
||||
&o->internal.result) < 0) {
|
||||
ret = -1;
|
||||
goto done;
|
||||
}
|
||||
|
||||
if (!o->skip_cache_tree_update &&
|
||||
!cache_tree_fully_valid(o->internal.result.cache_tree))
|
||||
cache_tree_update(&o->internal.result,
|
||||
|
||||
Reference in New Issue
Block a user