From: Sergey Vlasov <vsu@altlinux.ru>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Martin Koegler <mkoegler@auto.tuwien.ac.at>
Subject: Re: [PATCH] fsck.c: fix bogus "empty tree" check
Date: Tue, 4 Mar 2008 15:26:35 +0300 [thread overview]
Message-ID: <20080304152635.40451f7c.vsu@altlinux.ru> (raw)
In-Reply-To: <7vbq5u91lf.fsf@gitster.siamese.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 3175 bytes --]
On Tue, 04 Mar 2008 03:21:16 -0800 Junio C Hamano wrote:
> * I've wasted a few hours tonight hunting for random breakages in "git
> push", the symptom of which is "fatal: unresolved deltas left after
> unpacking." I was hoping this patch would fix it, but it seems that
> the problem is elsewhere.
>
> I'll revert the following two commits for now:
>
> d5ef408 (unpack-objects: prevent writing of inconsistent objects)
> 28f72a0 (receive-pack: use strict mode for unpacking objects)
>
> as I have verified that running with receive.fsckobjects set to false
> fixes the issues for me, and the repository at the receiving end (both
> before and after the push) pass git-fsck without problems. Needless to
> say, I am not a happy camper right now.
This part of commit d5ef408 changes is bogus:
> @@ -144,9 +205,36 @@ static void added_object(unsigned nr, enum object_type type,
> static void write_object(unsigned nr, enum object_type type,
> void *buf, unsigned long size)
> {
> - if (write_sha1_file(buf, size, typename(type), obj_list[nr].sha1) < 0)
> - die("failed to write object");
> added_object(nr, type, buf, size);
The write_sha1_file() call here was calculating obj_list[nr].sha1; now
it is removed, but added_object() needs this value:
| static void added_object(unsigned nr, enum object_type type,
| void *data, unsigned long size)
| {
| struct delta_info **p = &delta_list;
| struct delta_info *info;
|
| while ((info = *p) != NULL) {
| if (!hashcmp(info->base_sha1, obj_list[nr].sha1) ||
^^^^^^^^^^^^^^^^^
| info->base_offset == obj_list[nr].offset) {
| *p = info->next;
| p = &delta_list;
| resolve_delta(info->nr, type, data, size,
| info->delta, info->size);
| free(info);
| continue;
| }
| p = &info->next;
| }
| }
However, I do not have time to create a proper test case for this.
> + if (!strict) {
> + if (write_sha1_file(buf, size, typename(type), obj_list[nr].sha1) < 0)
> + die("failed to write object");
> + free(buf);
> + obj_list[nr].obj = 0;
> + } else if (type == OBJ_BLOB) {
> + struct blob *blob;
> + if (write_sha1_file(buf, size, typename(type), obj_list[nr].sha1) < 0)
> + die("failed to write object");
> + free(buf);
> +
> + blob = lookup_blob(obj_list[nr].sha1);
> + if (blob)
> + blob->object.flags |= FLAG_WRITTEN;
> + else
> + die("invalid blob object");
> + obj_list[nr].obj = 0;
> + } else {
> + struct object *obj;
> + int eaten;
> + hash_sha1_file(buf, size, typename(type), obj_list[nr].sha1);
> + obj = parse_object_buffer(obj_list[nr].sha1, type, size, buf, &eaten);
> + if (!obj)
> + die("invalid %s", typename(type));
> + /* buf is stored via add_object_buffer and in obj, if its a tree or commit */
> + add_object_buffer(obj, buf, size);
> + obj->flags |= FLAG_OPEN;
> + obj_list[nr].obj = obj;
> + }
> }
>
> static void resolve_delta(unsigned nr, enum object_type type,
The simplest way to fix this would be to duplicate the added_object()
call in all branches; invoking hash_sha1_file() unconditionally will
work too, but may be wasteful if we need to call write_sha1_file()
afterwards.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-03-04 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 11:21 [PATCH] fsck.c: fix bogus "empty tree" check Junio C Hamano
2008-03-04 12:26 ` Sergey Vlasov [this message]
2008-03-04 19:57 ` Junio C Hamano
2008-03-05 8:47 ` [PATCH] t5300: add test for "unpack-objects --strict" Junio C Hamano
2008-03-05 9:17 ` [PATCH v2] " Junio C Hamano
2008-03-04 21:48 ` [PATCH] fsck.c: fix bogus "empty tree" check Martin Koegler
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080304152635.40451f7c.vsu@altlinux.ru \
--to=vsu@altlinux.ru \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mkoegler@auto.tuwien.ac.at \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).