From: Junio C Hamano <gitster@pobox.com>
To: Nicolas Pitre <nico@cam.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/4] make verify_one_pack() a bit less wrong wrt packed_git structure
Date: Sat, 01 Mar 2008 12:25:34 -0800 [thread overview]
Message-ID: <7vwsomxkch.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: alpine.LFD.1.00.0803010305230.2899@xanadu.home
Nicolas Pitre <nico@cam.org> writes:
>> I just quickly looked at verify_packfile() after applying your
>> series, and it seems that nothing tries to access objects with
>> only their SHA-1 names without explicitly telling which pack to
>> read from, so it should still be safe even if we did not install
>> the packed git (iow, the normal codepath would not try to pick
>> up objects from the suspect pack that is being validated).
>>
>> But it made me feel a bit worried.
>
> The problem is with the patch that follows, which calls init_revindex().
Oh, Ok.
I see nobody other than pack-check calls packed_object_info_detail, and
that would be the only codepath that would load revindex in-core, so the
change would be fine. I was worried about having to load revindex which
would not help anything but info-detail which is pretty much useless for
most operations.
prev parent reply other threads:[~2008-03-01 20:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 5:25 [PATCH 0/4] enhancements to 'git verify-pack' Nicolas Pitre
2008-02-28 5:25 ` [PATCH 1/4] factorize revindex code out of builtin-pack-objects.c Nicolas Pitre
2008-02-28 5:25 ` [PATCH 2/4] make verify_one_pack() a bit less wrong wrt packed_git structure Nicolas Pitre
2008-02-28 5:25 ` [PATCH 3/4] fix unimplemented packed_object_info_detail() features Nicolas Pitre
2008-02-28 5:25 ` [PATCH 4/4] add storage size output to 'git verify-pack -v' Nicolas Pitre
2008-03-01 5:59 ` [PATCH 2/4] make verify_one_pack() a bit less wrong wrt packed_git structure Junio C Hamano
2008-03-01 8:18 ` Nicolas Pitre
2008-03-01 20:25 ` Junio C Hamano [this message]
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=7vwsomxkch.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=nico@cam.org \
/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).