From cd13762d8f837b6339b7d9f3090c0de44d3e01aa Mon Sep 17 00:00:00 2001 From: Elijah Newren Date: Thu, 15 Nov 2018 23:59:52 -0800 Subject: fast-export: when using paths, avoid corrupt stream with non-existent mark If file paths are specified to fast-export and multiple refs point to a commit that does not touch any of the relevant file paths, then fast-export can hit problems. fast-export has a list of additional refs that it needs to explicitly set after exporting all blobs and commits, and when it tries to get_object_mark() on the relevant commit, it can get a mark of 0, i.e. "not found", because the commit in question did not touch the relevant paths and thus was not exported. Trying to import a stream with a mark corresponding to an unexported object will cause fast-import to crash. Avoid this problem by taking the commit the ref points to and finding an ancestor of it that was exported, and make the ref point to that commit instead. Signed-off-by: Elijah Newren Acked-by: Jeff King Signed-off-by: Junio C Hamano --- t/t9350-fast-export.sh | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) (limited to 't') diff --git a/t/t9350-fast-export.sh b/t/t9350-fast-export.sh index 3400ebeb51..299120ba70 100755 --- a/t/t9350-fast-export.sh +++ b/t/t9350-fast-export.sh @@ -382,6 +382,26 @@ test_expect_success 'path limiting with import-marks does not lose unmodified fi grep file0 actual ' +test_expect_success 'avoid corrupt stream with non-existent mark' ' + test_create_repo avoid_non_existent_mark && + ( + cd avoid_non_existent_mark && + + test_commit important-path && + + test_commit ignored && + + git branch A && + git branch B && + + echo foo >>important-path.t && + git add important-path.t && + test_commit more changes && + + git fast-export --all -- important-path.t | git fast-import --force + ) +' + test_expect_success 'full-tree re-shows unmodified files' ' git checkout -f simple && git fast-export --full-tree simple >actual && -- cgit v1.2.3