From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: Aaron Plattner <aplattner@nvidia.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2025, #03)
Date: Thu, 18 Dec 2025 07:22:44 +0100 [thread overview]
Message-ID: <aUOdtDrmtGtQg596@pks.im> (raw)
In-Reply-To: <xmqqtsxoxzs5.fsf@gitster.g>
On Thu, Dec 18, 2025 at 11:57:30AM +0900, Junio C Hamano wrote:
> Aaron Plattner <aplattner@nvidia.com> writes:
>
> > I'm pretty sure the problem is when do_oid_object_info_extended()
> > substitutes the blank oi here:
> >
> > if (!oi)
> > oi = &blank_oi;
> >
> > and then packfile_store_read_object_info() compares it to its own local
> > blank oi:
> >
> > static struct object_info blank_oi = OBJECT_INFO_INIT;
>
> Ahh, that's an unusual mistake.
>
> The following was done on top of 'seen', but would it help? We
> shouldn't have to use the stand-in "blank" thing to begin with.
>
> Besides, explicitly handling the NULL case would reduce the
> potential chance of errors that somebody accidentally writes into
> blank_oi, making its contents dirty.
Yeah, indeed I've already found that regression myself and got it
cooking in a local patch series. I was holding off from sending that
series because there was a minor conflict with an in-flight one. But
I'll take this opportunity and send it out now.
Thanks for the report and your initial triaging, Junio!
Patrick
prev parent reply other threads:[~2025-12-18 6:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 10:26 What's cooking in git.git (Dec 2025, #03) Junio C Hamano
2025-12-13 7:42 ` Adrian Ratiu
2025-12-16 1:59 ` Junio C Hamano
2025-12-16 8:13 ` Patrick Steinhardt
2025-12-16 10:41 ` Adrian Ratiu
2025-12-16 17:49 ` Emily Shaffer
2025-12-17 5:04 ` Junio C Hamano
2025-12-13 18:45 ` René Scharfe
2025-12-17 0:09 ` Aaron Plattner
2025-12-17 5:02 ` Junio C Hamano
2025-12-17 5:20 ` Aaron Plattner
2025-12-17 6:18 ` Jeff King
2025-12-17 13:46 ` Junio C Hamano
2025-12-17 20:26 ` Aaron Plattner
2025-12-18 2:57 ` Junio C Hamano
2025-12-18 6:22 ` Patrick Steinhardt [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=aUOdtDrmtGtQg596@pks.im \
--to=ps@pks.im \
--cc=aplattner@nvidia.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).