From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, Kyle Lippincott <spectral@google.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: MSan failures in pack-bitmap
Date: Sun, 9 Jun 2024 16:30:25 -0400 [thread overview]
Message-ID: <ZmYQ4f+qmQIxf+5g@nand.local> (raw)
In-Reply-To: <xmqqh6e1c1bf.fsf@gitster.g>
On Sun, Jun 09, 2024 at 01:23:48PM -0700, Junio C Hamano wrote:
> Taylor Blau <me@ttaylorr.com> writes:
>
> > I don't think the issue here is a corrupt on-disk bitmap or MIDX. The
> > regression that Kyle reported was a logic issue reading a
> > ordinary/non-corrupt MIDX file, not a result of some on-disk corruption.
> > ...
> > But I do not think that repository corruption is a likely outcome here,
>
> Yes, exactly. What I was asking was how on-disk corruption that
> would result from the logic issue of reading a correct MIDX file.
OK, I think I misunderstood your original email.
> ... there is no reasonable work around here, is there? We do not
> even know exactly what kind of breakage this will cause (which is
> expected, as we would be "reading" a garbage value and basing future
> actions on it)?
I think the end-result would be that packs sent between client and
server during fetches or pushes would be broken, resulting in index-pack
failing to index them, thus causing one side or the other to (correctly)
throw away the received pack.
The only thing I can think of to avoid this would be to enable
multi-pack reuse, which is only possible if your MIDX has a BTMP chunk.
The other work around would be to disable pack-reuse altogether, which
is very unfortunate.
Thanks,
Taylor
next prev parent reply other threads:[~2024-06-09 20:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-08 2:43 MSan failures in pack-bitmap Kyle Lippincott
2024-06-08 8:18 ` Jeff King
2024-06-09 15:31 ` Taylor Blau
2024-06-09 18:55 ` Junio C Hamano
2024-06-09 20:00 ` Taylor Blau
2024-06-09 20:23 ` Junio C Hamano
2024-06-09 20:30 ` Taylor Blau [this message]
2024-06-09 20:24 ` Taylor Blau
2024-06-11 8:02 ` Jeff King
2024-06-11 9:12 ` Jeff King
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=ZmYQ4f+qmQIxf+5g@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=spectral@google.com \
/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).