From: Derrick Stolee <stolee@gmail.com>
To: "D. Ben Knoble" <ben.knoble@gmail.com>,
Yuvraj Singh Chauhan <ysinghcin@gmail.com>
Cc: git@vger.kernel.org, christian.couder@gmail.com
Subject: Re: [PATCH v1] path-walk: fix NULL pointer dereference in error message
Date: Fri, 20 Mar 2026 12:14:19 -0400 [thread overview]
Message-ID: <994f92e9-3576-455a-a142-0fefc559131c@gmail.com> (raw)
In-Reply-To: <CALnO6CDnwYaAPhp67kaYWtV48ULjWAR6ks1khVXmSs1oWUbRDQ@mail.gmail.com>
On 3/20/2026 11:16 AM, D. Ben Knoble wrote:
> On Fri, Mar 20, 2026 at 7:50 AM Yuvraj Singh Chauhan
> <ysinghcin@gmail.com> wrote:
>> @@ -171,7 +171,7 @@ static int add_tree_entries(struct path_walk_context *ctx,
>>
>> if (!o) {
>> error(_("failed to find object %s"),
>> - oid_to_hex(&o->oid));
>> + oid_to_hex(&entry.oid));
>> return -1;
>> }
>>
>> --
>> 2.53.0.582.gca1db8a0f7
>
> Interesting find. I was hoping to see an easy way to reproduce hitting
> this code, and after grepping around a bit I found a few places that
> end up in this code (git-backfill and git-repo being the primary
> callers of walk_objects_by_path), but on second glance I think "!o" is
> current dead code.
I can appreciate that the existing code is clearly incorrect, so
tooling scanning code for defects would find this even if we can't
easily create a test case to demonstrate it.
> Still, fixing such obviously wrong dereference is good, but I wonder
> if we should go further?
>
> You mentioned git-backfill with a tree missing from the local odb; do
> you have a short reproduction script or test-case?
I imagine that it would be difficult to set up such a case, but maybe
it would follow these steps (based on existing 'git backfill' tests
that start with a partial clone):
1. Make a bare, blobless partial clone of the server repo.
2. Explode the client repo's object store into loose objects.
3. Delete a loose tree object, but one that isn't a commit's root
tree. It must be a child tree.
In this case, we should hit this issue. Blobless partial clones
expect all reachable trees to exist locally and so are not prepared
to download missing trees on-demand.
Thanks,
-Stolee
next prev parent reply other threads:[~2026-03-20 16:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 11:48 [PATCH v1] path-walk: fix NULL pointer dereference in error message Yuvraj Singh Chauhan
2026-03-20 15:16 ` D. Ben Knoble
2026-03-20 16:14 ` Derrick Stolee [this message]
2026-03-23 9:45 ` Yuvraj Singh Chauhan
2026-03-20 17:08 ` Junio C Hamano
2026-03-20 18:54 ` René Scharfe
2026-03-22 14:21 ` D. Ben Knoble
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=994f92e9-3576-455a-a142-0fefc559131c@gmail.com \
--to=stolee@gmail.com \
--cc=ben.knoble@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=ysinghcin@gmail.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