Fix tar2vhd on specific unordered tars #1012
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This addresses nil dereference bug we encountered when doing tar2vhd conversion and extends on the previous fix to address when parent directories don't exist.
In this case the issue arises if the root directory has not yet been initialized by the time a file not in the root directory is processed. For the bug to happen the tar has to be built in such a way that the first file processed:
In the particular case of the image for which we found the issue the first file seen looked something like: /folder1/folder2/somefile which meets all the conditions above causing the failure. As a note I swapped the order in the test at tar2ext4_test.go to show how to replicate and to include the scenario of this fix there.
As a fix I am calling finishInode at the start of CreateWithParents following the convention of Create and the other methods which rely on its init check and state cleanup