)]}' { "commit": "b7af332bfdd208a563186f847dfce2eeb1e75669", "tree": "9ad03bc3ffb5d123371efd87571781bbd93a6268", "parents": [ "e431c649e5d0824b1776fbe3acfaa923f5c5ac43" ], "author": { "name": "Eric Sandeen", "email": "sandeen@redhat.com", "time": "Thu Oct 18 23:02:05 2012 -0500" }, "committer": { "name": "Ben Myers", "email": "bpm@sgi.com", "time": "Fri Nov 02 12:21:17 2012 -0500" }, "message": "xfsdump: fill in bs_forkoff\n\nUpstream, the structure containing bs_forkoff is actually zeroed\nprior to these functions, but when pulling the patch back to an\nolder xfsdump, we got checksum errors due to an uninitialized\nbs_forkoff not matching in dump vs. restore.\n\nSo even though forkoff won\u0027t be explicitly restored from\na dump, do explicitly set it in these routines to keep checksums\nhappy.\n\nThis fixes \u0027bad header checksum\u0027 errors in xfsrestore, which were\nintroduced by commit 1e309da7.\n\nSigned-off-by: Eric Sandeen \u003csandeen@redhat.com\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Ben Myers \u003cbpm@sgi.com\u003e\n", "tree_diff": [ { "type": "modify", "old_id": "e42abd51db90314a16a3b554085d21c1d31be3b8", "old_mode": 33188, "old_path": "common/arch_xlate.c", "new_id": "bafc1a6c693dad1c25933edf8e58afc33d8cb8ea", "new_mode": 33188, "new_path": "common/arch_xlate.c" }, { "type": "modify", "old_id": "ec5e9540be29f39fd3353f60e996473bb846a1e3", "old_mode": 33188, "old_path": "dump/content.c", "new_id": "9a36fe100ad9aa5286944b18906221ba3757d4e9", "new_mode": 33188, "new_path": "dump/content.c" } ] }