git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 2/2] fsck: treat a NUL in a tag header as an error

From
René Scharfe <l.s.r@web.de>
Date
Nov 19, 2015, 16:25 UTC
Message-ID
<564DF7FB.3090704@web.de>
In-Reply-To
<564DF6BE.6020609@web.de>

We check the return value of verify_header() for commits already, so do the same for tags as well.

Signed-off-by: Rene Scharfe <l.s.r@web.de>
---
 fsck.c          | 3 ++-
 t/t1450-fsck.sh | 2 +-
 2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/fsck.c b/fsck.c
index e41e753..4060f1f 100644
--- a/fsck.c
+++ b/fsck.c
@@ -711,7 +711,8 @@ static int fsck_tag_buffer(struct tag *tag, const char *data,
 		}
 	}
 
-	if (verify_headers(buffer, size, &tag->object, options))
+	ret = verify_headers(buffer, size, &tag->object, options);
+	if (ret)
 		goto done;
 
 	if (!skip_prefix(buffer, "object ", &buffer)) {
diff --git a/t/t1450-fsck.sh b/t/t1450-fsck.sh
index 6c96953..e66b7cb 100755
--- a/t/t1450-fsck.sh
+++ b/t/t1450-fsck.sh
@@ -288,7 +288,7 @@ test_expect_success 'tag with bad tagger' '
 	grep "error in tag .*: invalid author/committer" out
 '
 
-test_expect_failure 'tag with NUL in header' '
+test_expect_success 'tag with NUL in header' '
 	sha=$(git rev-parse HEAD) &&
 	q_to_nul >tag-NUL-header <<-EOF &&
 	object $sha
-- 
2.6.3
Previous: René ScharfeNext: Jeff King
Message 2 of 14 in “t1450: add tests for NUL in headers of commits and tags”
  1. 1/2 t1450: add tests for NUL in headers of commits and tagsRené Scharfe, Nov 19, 2015
  2. 2/2 fsck: treat a NUL in a tag header as an errorRené Scharfe, Nov 19, 2015
  3. Jeff KingNov 20, 2015
  4. Johannes SchindelinNov 20, 2015
  5. Eric SunshineNov 19, 2015
  6. René ScharfeNov 19, 2015
  7. Jeff KingNov 20, 2015
  8. René ScharfeNov 20, 2015
  9. 3/2 test: factor out helper function test_must_containRené Scharfe, Nov 20, 2015
  10. Johannes SixtNov 21, 2015
  11. René ScharfeNov 21, 2015
  12. 4/2 test: use test_must_containRené Scharfe, Nov 20, 2015
  13. SZEDER GáborNov 21, 2015
  14. René ScharfeNov 21, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.