From: Taylor Blau <me@ttaylorr.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
Derrick Stolee <derrickstolee@github.com>
Subject: [PATCH v2 5/5] commit-graph: avoid repeated mixed generation number warnings
Date: Fri, 11 Aug 2023 13:05:54 -0400 [thread overview]
Message-ID: <b82b15ebc86168223619c2b853e0abe02831138b.1691773533.git.me@ttaylorr.com> (raw)
In-Reply-To: <cover.1691773533.git.me@ttaylorr.com>
When validating that a commit-graph has either all zero, or all non-zero
generation numbers, we emit a warning on both the rising and falling
edge of transitioning between the two.
So if we are unfortunate enough to see a commit-graph which has a
repeating sequence of zero, then non-zero generation numbers, we'll
generate many warnings that contain more or less the same information.
Avoid this by treating `generation_zero` as a bit-field, and warn under
the same conditions, but only do so once.
Suggested-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Taylor Blau <me@ttaylorr.com>
---
commit-graph.c | 17 ++++++++++-------
t/t5318-commit-graph.sh | 14 ++++++++++++++
2 files changed, 24 insertions(+), 7 deletions(-)
diff --git a/commit-graph.c b/commit-graph.c
index f7d9b31546..8d924b4509 100644
--- a/commit-graph.c
+++ b/commit-graph.c
@@ -2562,6 +2562,8 @@ static void graph_report(const char *fmt, ...)
#define GENERATION_ZERO_EXISTS 1
#define GENERATION_NUMBER_EXISTS 2
+#define GENERATION_NUMBER_BOTH_EXIST \
+ (GENERATION_ZERO_EXISTS | GENERATION_NUMBER_EXISTS)
static int commit_graph_checksum_valid(struct commit_graph *g)
{
@@ -2573,19 +2575,19 @@ static void verify_mixed_generation_numbers(struct commit_graph *g,
int *generation_zero)
{
if (commit_graph_generation_from_graph(graph_commit)) {
- if (*generation_zero == GENERATION_ZERO_EXISTS)
+ if (*generation_zero & GENERATION_ZERO_EXISTS)
graph_report(_("commit-graph has non-zero generation "
"number for commit %s, but zero "
"elsewhere"),
oid_to_hex(&graph_commit->object.oid));
- *generation_zero = GENERATION_NUMBER_EXISTS;
+ *generation_zero |= GENERATION_NUMBER_EXISTS;
} else {
- if (*generation_zero == GENERATION_NUMBER_EXISTS)
+ if (*generation_zero & GENERATION_NUMBER_EXISTS)
graph_report(_("commit-graph has generation number "
"zero for commit %s, but non-zero "
"elsewhere"),
oid_to_hex(&graph_commit->object.oid));
- *generation_zero = GENERATION_ZERO_EXISTS;
+ *generation_zero |= GENERATION_ZERO_EXISTS;
}
}
@@ -2702,10 +2704,11 @@ static int verify_one_commit_graph(struct repository *r,
graph_report(_("commit-graph parent list for commit %s terminates early"),
oid_to_hex(&cur_oid));
- verify_mixed_generation_numbers(g, graph_commit,
- &generation_zero);
+ if (generation_zero != GENERATION_NUMBER_BOTH_EXIST)
+ verify_mixed_generation_numbers(g, graph_commit,
+ &generation_zero);
- if (generation_zero == GENERATION_ZERO_EXISTS)
+ if (generation_zero & GENERATION_ZERO_EXISTS)
continue;
/*
diff --git a/t/t5318-commit-graph.sh b/t/t5318-commit-graph.sh
index 8e96471b34..2626d41c94 100755
--- a/t/t5318-commit-graph.sh
+++ b/t/t5318-commit-graph.sh
@@ -628,6 +628,20 @@ test_expect_success 'detect mixed generation numbers (zero to non-zero)' '
"but zero elsewhere"
'
+test_expect_success 'detect mixed generation numbers (flip-flop)' '
+ corrupt_graph_setup &&
+ for pos in \
+ $GRAPH_BYTE_COMMIT_GENERATION \
+ $GRAPH_BYTE_COMMIT_GENERATION_LAST
+ do
+ printf "\0\0\0\0" | dd of="full/$objdir/info/commit-graph" bs=1 \
+ seek="$pos" conv=notrunc || return 1
+ done &&
+
+ test_must_fail git -C full commit-graph verify 2>err &&
+ test 1 -eq "$(grep -c "generation number" err)"
+'
+
test_expect_success 'git fsck (checks commit-graph when config set to true)' '
git -C full fsck &&
corrupt_graph_and_verify $GRAPH_BYTE_FOOTER "\00" \
--
2.42.0.rc0.30.gb82b15ebc8
next prev parent reply other threads:[~2023-08-11 17:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 19:15 [RFC/PATCH] commit-graph: verify swapped zero/non-zero generation cases Jeff King
2023-08-10 16:00 ` Taylor Blau
2023-08-10 17:44 ` Taylor Blau
2023-08-10 20:37 ` [PATCH 0/4] commit-graph: fsck zero/non-zero generation number fixes Taylor Blau
2023-08-10 20:37 ` [PATCH 1/4] commit-graph: introduce `commit_graph_generation_from_graph()` Taylor Blau
2023-08-10 20:37 ` [PATCH 2/4] commit-graph: verify swapped zero/non-zero generation cases Taylor Blau
2023-08-10 21:36 ` Junio C Hamano
2023-08-11 15:01 ` Jeff King
2023-08-11 17:08 ` Taylor Blau
2023-08-10 20:37 ` [PATCH 3/4] t/t5318-commit-graph.sh: test generation zero transitions during fsck Taylor Blau
2023-08-10 20:37 ` [PATCH 4/4] commit-graph: invert negated conditional Taylor Blau
2023-08-11 15:02 ` [PATCH 0/4] commit-graph: fsck zero/non-zero generation number fixes Jeff King
2023-08-11 17:05 ` [PATCH v2 0/5] " Taylor Blau
2023-08-11 17:05 ` [PATCH v2 1/5] commit-graph: introduce `commit_graph_generation_from_graph()` Taylor Blau
2023-08-11 17:05 ` [PATCH v2 2/5] commit-graph: verify swapped zero/non-zero generation cases Taylor Blau
2023-08-11 17:05 ` [PATCH v2 3/5] t/t5318-commit-graph.sh: test generation zero transitions during fsck Taylor Blau
2023-08-11 17:05 ` [PATCH v2 4/5] commit-graph: invert negated conditional, extract to function Taylor Blau
2023-08-11 17:05 ` Taylor Blau [this message]
2023-08-11 17:58 ` [PATCH v2 0/5] commit-graph: fsck zero/non-zero generation number fixes Jeff King
2023-08-11 19:28 ` Junio C Hamano
2023-08-17 19:51 ` Jeff King
2023-08-21 21:25 ` Taylor Blau
2023-08-21 21:34 ` [PATCH v3 0/4] " Taylor Blau
2023-08-21 21:34 ` [PATCH v3 1/4] commit-graph: introduce `commit_graph_generation_from_graph()` Taylor Blau
2023-08-21 21:34 ` [PATCH v3 2/4] commit-graph: verify swapped zero/non-zero generation cases Taylor Blau
2023-08-21 21:34 ` [PATCH v3 3/4] t/t5318-commit-graph.sh: test generation zero transitions during fsck Taylor Blau
2023-08-21 21:34 ` [PATCH v3 4/4] commit-graph: commit-graph: avoid repeated mixed generation number warnings Taylor Blau
2023-08-21 21:55 ` [PATCH v3 0/4] commit-graph: fsck zero/non-zero generation number fixes Jeff King
2023-08-21 23:22 ` Junio C Hamano
2023-08-23 19:59 ` Taylor Blau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b82b15ebc86168223619c2b853e0abe02831138b.1691773533.git.me@ttaylorr.com \
--to=me@ttaylorr.com \
--cc=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).