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

Re: RE: [External Mail]Re: Git fork process infinitely and never stop

From
Llilinchao@oschina.cn <lilinchao@oschina.cn>
Date
Jul 6, 2022, 07:21 UTC
Message-ID
<202207061520052718298@oschina.cn>
In-Reply-To
<8ccd27ef3a344596b6237e98e1a5f204@xiaomi.com>
Show 5 quoted lines
>- git version:
>2.36.1
>- steps to reproduce the bug
>: We have no idea actually. We're maintainer of our internal git/gerrit. We found sometimes some user will invoke 100+ threads to clone the same repository. And when we ask those guy, they say they only executed the "git fetch" once. And just like the youtube videio, you will find git fork a child git, and then grandson child git, and loop like this forever until the server down.
>If we copy their local repository to our own PC, and then execute `git fetch`, we can also reproduce it. It seems that some broken local git files cause this bug 
So the repo "git/gerrit" is hosted in your local? and how you "copy" it to your own PC? 
Previous: Johannes SixtNext: 程洋
Message 6 of 14 in “Git fork process infinitely and never stop”
  1. 程洋Jul 4, 2022
  2. Bagas SanjayaJul 5, 2022
  3. 程洋Jul 5, 2022
  4. Ævar Arnfjörð BjarmasonJul 5, 2022
  5. Johannes SixtJul 6, 2022
  6. lilinchao@oschina.cnJul 6, 2022
  7. 回复: RE: [External Mail]Re: Git fork process infinitely and never stop程洋, Jul 6, 2022
  8. 程洋Jul 7, 2022
  9. 程洋Jul 8, 2022
  10. possible bug with commit-graph causing git to fork bomb (was Re: [External Mail]Re: Git fork process infinitely and never stop)Carlo Marcelo Arenas Belón, Jul 9, 2022
  11. Han XinJul 9, 2022
  12. Carlo ArenasJul 9, 2022
  13. 程洋Jul 11, 2022
  14. 程洋Sep 27, 2022

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.