Browse Source

upload-pack: disable commit graph more gently for shallow traversal

When the client has asked for certain shallow options like
"deepen-since", we do a custom rev-list walk that pretends to be
shallow. Before doing so, we have to disable the commit-graph, since it
is not compatible with the shallow view of the repository. That's
handled by 829a321569 (commit-graph: close_commit_graph before shallow
walk, 2018-08-20). That commit literally closes and frees our
repo->objects->commit_graph struct.

That creates an interesting problem for commits that have _already_ been
parsed using the commit graph. Their commit->object.parsed flag is set,
their commit->graph_pos is set, but their commit->maybe_tree may still
be NULL. When somebody later calls repo_get_commit_tree(), we see that
we haven't loaded the tree oid yet and try to get it from the commit
graph. But since it has been freed, we segfault!

So the root of the issue is a data dependency between the commit's
lazy-load of the tree oid and the fact that the commit graph can go
away mid-process. How can we resolve it?

There are a couple of general approaches:

  1. The obvious answer is to avoid loading the tree from the graph when
     we see that it's NULL. But then what do we return for the tree oid?
     If we return NULL, our caller in do_traverse() will rightly
     complain that we have no tree. We'd have to fallback to loading the
     actual commit object and re-parsing it. That requires teaching
     parse_commit_buffer() to understand re-parsing (i.e., not starting
     from a clean slate and not leaking any allocated bits like parent
     list pointers).

  2. When we close the commit graph, walk through the set of in-memory
     objects and clear any graph_pos pointers. But this means we also
     have to "unparse" any such commits so that we know they still need
     to open the commit object to fill in their trees. So it's no less
     complicated than (1), and is more expensive (since we clear objects
     we might not later need).

  3. Stop freeing the commit-graph struct. Continue to let it be used
     for lazy-loads of tree oids, but let upload-pack specify that it
     shouldn't be used for further commit parsing.

  4. Push the whole shallow rev-list out to its own sub-process, with
     the commit-graph disabled from the start, giving it a clean memory
     space to work from.

I've chosen (3) here. Options (1) and (2) would work, but are
non-trivial to implement. Option (4) is more expensive, and I'm not sure
how complicated it is (shelling out for the actual rev-list part is
easy, but we do then parse the resulting commits internally, and I'm not
clear which parts need to be handling shallow-ness).

The new test in t5500 triggers this segfault, but see the comments there
for how horribly intimate it has to be with how both upload-pack and
commit graphs work.

Signed-off-by: Jeff King <>
Signed-off-by: Junio C Hamano <>
Jeff King Junio C Hamano 3 months ago
5 changed files with 60 additions and 1 deletions
  1. +12
  2. +6
  3. +3
  4. +38
  5. +1

+ 12
- 0
commit-graph.c View File

@@ -468,6 +468,13 @@ static int prepare_commit_graph(struct repository *r)
struct object_directory *odb;

* This must come before the "already attempted?" check below, because
* we want to disable even an already-loaded graph file.
if (r->commit_graph_disabled)
return 0;

if (r->objects->commit_graph_attempted)
return !!r->objects->commit_graph;
r->objects->commit_graph_attempted = 1;
@@ -2101,3 +2108,8 @@ void free_commit_graph(struct commit_graph *g)

void disable_commit_graph(struct repository *r)
r->commit_graph_disabled = 1;

+ 6
- 0
commit-graph.h View File

@@ -107,4 +107,10 @@ int verify_commit_graph(struct repository *r, struct commit_graph *g, int flags)
void close_commit_graph(struct raw_object_store *);
void free_commit_graph(struct commit_graph *);

* Disable further use of the commit graph in this process when parsing a
* "struct commit".
void disable_commit_graph(struct repository *r);


+ 3
- 0
repository.h View File

@@ -124,6 +124,9 @@ struct repository {
/* A unique-id for tracing purposes. */
int trace2_repo_id;

/* True if commit-graph has been disabled within this process. */
int commit_graph_disabled;

/* Configurations */

/* Indicate if a repository has a different 'commondir' from 'gitdir' */

+ 38
- 0
t/ View File

@@ -783,6 +783,44 @@ test_expect_success 'clone shallow since selects no commits' '

# A few subtle things about the request in this test:
# - the server must have commit-graphs present and enabled
# - the history is such that our want/have share a common ancestor ("base"
# here)
# - we send only a single have, which is fewer than a normal client would
# send. This ensures that we don't parse "base" up front with
# parse_object(), but rather traverse to it as a parent while deciding if we
# can stop the "have" negotiation, and call parse_commit(). The former
# sees the actual object data and so always loads the three oid, whereas the
# latter will try to load it lazily.
# - we must use protocol v2, because it handles the "have" negotiation before
# processing the shallow directives
test_expect_success 'shallow since with commit graph and already-seen commit' '
test_create_repo shallow-since-graph &&
cd shallow-since-graph &&
test_commit base &&
test_commit master &&
git checkout -b other HEAD^ &&
test_commit other &&
git commit-graph write --reachable &&
git config core.commitGraph true &&

GIT_PROTOCOL=version=2 git upload-pack . <<-EOF >/dev/null
00010013deepen-since 1
0032want $(git rev-parse other)
0032have $(git rev-parse master)

test_expect_success 'shallow clone exclude tag two' '
test_create_repo shallow-exclude &&

+ 1
- 1
upload-pack.c View File

@@ -722,7 +722,7 @@ static void deepen_by_rev_list(struct packet_writer *writer, int ac,
struct commit_list *result;

result = get_shallow_commits_by_rev_list(ac, av, SHALLOW, NOT_SHALLOW);
send_shallow(writer, result);