Re: [PATCH v2 5/7] reftable: ensure that obj_id_len is >= 2 on writing
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Feb 18, 2022, 00:01 UTC
- Message-ID
- <xmqq8ru959fz.fsf@gitster.g>
- In-Reply-To
- <2bd3d44ba57ddb43c09367b45a8f056233d465e9.1645106124.git.gitgitgadget@gmail.com>
"Han-Wen Nienhuys via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 12 quoted lines
> diff --git a/reftable/writer.c b/reftable/writer.c
> index d54215a50dc..5e4e6e93416 100644
> --- a/reftable/writer.c
> +++ b/reftable/writer.c
> @@ -515,7 +515,9 @@ static void object_record_free(void *void_arg, void *key)
> static int writer_dump_object_index(struct reftable_writer *w)
> {
> struct write_record_arg closure = { .w = w };
> - struct common_prefix_arg common = { NULL };
> + struct common_prefix_arg common = {
> + .max = 1, /* obj_id_len should be >= 2. */
> + };It feels somewhat strange that we have to set .max to set the floor for the minimum length, but given the way update_common() uses and maintains the member, it is more like "max size we have seen so far", and by pretending that we have already seen common prefix of length 1, we'd force ourselves that we need at least 2 to differentiate.
> if (w->obj_index_tree) {
> infix_walk(w->obj_index_tree, &update_common, &common);
> }