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

Seg Fault on git fetch with fetch.negotiationAlgorithm=skipping

From
Son Luong Ngoc <sluongng@gmail.com>
Date
Apr 30, 2020, 14:55 UTC
Message-ID
<450D5CC7-113A-40D8-9CD4-53786198526D@gmail.com>
Hi folks,

We recently encountered a segfault during a git fetch strace output could be found https://gist.github.com/sluongng/e48327cc911c617ed2ef8578acc2ea34

The root cause was due to having `fetch.negotiationAlgorithm=skipping` The repo is about linux.git size with a few NULL commit that we have been using `fsck.skipList` on both server and client side to skip.

Is this and edge case for the new algorithm?

Cheers, Son Luong.

Next: Taylor Blau
Message 1 of 4 in “Seg Fault on git fetch with fetch.negotiationAlgorithm=skipping”
  1. Son Luong NgocApr 30, 2020
  2. Taylor BlauApr 30, 2020
  3. Son Luong NgocMay 1, 2020
  4. Taylor BlauMay 1, 2020

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.