git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Null pointer dereference in error pathway on git pull

From
JHJoshua Hudson <jhudson@cedaron.com>
Date
Jan 26, 2021, 23:01 UTC
Message-ID
<f8b3b05a-db46-1977-6fb4-ed13ac48e131@cedaron.com>
In-Reply-To
<YBCd2ZAumP65yrUK@coredump.intra.peff.net>
2.29.2; yeah it does look like it could be the same bug
On 1/26/2021 2:55 PM, Jeff King wrote:
Show 20 quoted lines
> On Tue, Jan 26, 2021 at 12:31:30PM -0800, Joshua Hudson wrote:
>
>>> git pull
>> remote: Azure Repos
>> remote: Found 452 objects to send. (157 ms)
>> Rfatal: the remote end hung up unexpectedly
>> fatal: early EOFs:  81% (367/452)
>> fatal: index-pack failed
>> warning: unable to unlink '(NULL)': Invalid argument
>>
>>
>> So it hits some kind of error (looks like network disconnect) and tries
>> to back out; passed a NULL pointer to unlink().
>>
>> Apologies if this has been submitted before. A search didn't find it.
> Which version of Git are you using? It sounds like the same bug fixed by
> 6031af387e (fetch-pack: disregard invalid pack lockfiles, 2020-11-30).
> That's in v2.30.0.
>
> -Peff
Previous: Jeff King
Message 3 of 3 in “Null pointer dereference in error pathway on git pull”
  1. Joshua HudsonJan 26, 2021
  2. Jeff KingJan 26, 2021
  3. Joshua HudsonJan 26, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.