Re: [PATCH 3/3] refs: fix segfault in `is_pseudoref()` when ref cannot be resolved
- From
Karthik Nayak <karthik.188@gmail.com>
- Date
- Apr 29, 2024, 20:44 UTC
- Message-ID
- <CAOLa=ZSqtGRVVHma-=XzErVdZ04sY_bGvk8qiabNdYzojS2ZhA@mail.gmail.com>
- In-Reply-To
- <b43e51d0-2814-4800-b8d5-cea5f79ce318@gmail.com>
Hey Phillip,
Phillip Wood <phillip.wood123@gmail.com> writes:
Show 24 quoted lines
> Hi Karthik > > On 29/04/2024 19:57, Karthik Nayak wrote: >> Phillip Wood <phillip.wood123@gmail.com> writes: >>>> via the uninitialized value when calling `is_null_oid()`, which causes >>>> us to segfault. >>>> >>>> It is somewhat questionable in the first place that we declare a ref to >>>> be a pseudorefe depending on whether it resolves to an object ID or not. >>> >>> If I remember rightly Karthik added that check to avoid the files >>> backend calling a file with a name that matched the pseudoref syntax a >>> pseudoref when it wasn't actually a pseudoref. >> >> Not sure I follow. I think it was strictly done to ensure we don't >> consider symrefs as pseudorefs [1]. > > Junio suggested using refs_read_ref_unsafe() to ensure we don't consider > symrefs as pseudorefs but your patch was already reading the ref to > ensure it was not some random file whose name matches the pseudoref syntax. > > Best Wishes > > Phillip
Oh yes. You're absolutely correct. I just didn't understand what you were referring to :)