From: "lilinchao@oschina.cn" <lilinchao@oschina.cn>
To: 程洋 <chengyang@xiaomi.com>, "Bagas Sanjaya" <bagasdotme@gmail.com>,
git <git@vger.kernel.org>
Cc: 何浩 <hehao@xiaomi.com>, "Xin7 Ma 马鑫" <maxin7@xiaomi.com>
Subject: Re: RE: [External Mail]Re: Git fork process infinitely and never stop
Date: Wed, 6 Jul 2022 15:21:06 +0800 [thread overview]
Message-ID: <202207061520052718298@oschina.cn> (raw)
In-Reply-To: 8ccd27ef3a344596b6237e98e1a5f204@xiaomi.com
>- 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?
next prev parent reply other threads:[~2022-07-06 7:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 9:44 Git fork process infinitely and never stop 程洋
2022-07-05 12:32 ` Bagas Sanjaya
2022-07-05 15:25 ` [External Mail]Re: " 程洋
2022-07-05 22:50 ` Ævar Arnfjörð Bjarmason
2022-07-06 5:34 ` Johannes Sixt
2022-07-06 7:21 ` lilinchao [this message]
2022-07-06 14:03 ` 回复: " 程洋
[not found] ` <11f76b2382934edcb97eb201f0a78a67@xiaomi.com>
2022-07-07 17:54 ` 程洋
2022-07-08 10:45 ` 程洋
2022-07-09 0:26 ` 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
2022-07-09 0:52 ` Han Xin
2022-07-09 6:39 ` Carlo Arenas
2022-07-11 4:11 ` 程洋
2022-09-27 14:25 ` 程洋
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=202207061520052718298@oschina.cn \
--to=lilinchao@oschina.cn \
--cc=bagasdotme@gmail.com \
--cc=chengyang@xiaomi.com \
--cc=git@vger.kernel.org \
--cc=hehao@xiaomi.com \
--cc=maxin7@xiaomi.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;
as well as URLs for NNTP newsgroup(s).