From: 程洋 <chengyang@xiaomi.com>
To: "lilinchao@oschina.cn" <lilinchao@oschina.cn>,
Bagas Sanjaya <bagasdotme@gmail.com>, git <git@vger.kernel.org>
Cc: 何浩 <hehao@xiaomi.com>, "Xin7 Ma 马鑫" <maxin7@xiaomi.com>,
凡军辉 <fanjunhui@xiaomi.com>, 石奉兵 <shifengbing@xiaomi.com>
Subject: RE: RE: [External Mail]Re: Git fork process infinitely and never stop
Date: Fri, 8 Jul 2022 10:45:08 +0000 [thread overview]
Message-ID: <bd33fa6079c2485fb6ee741be05d3f7e@xiaomi.com> (raw)
In-Reply-To: 11f76b2382934edcb97eb201f0a78a67@xiaomi.com
Any feedback on this?
-----Original Message-----
From: 程洋
Sent: Friday, July 8, 2022 1:54 AM
To: 'lilinchao@oschina.cn' <lilinchao@oschina.cn>; 'Bagas Sanjaya' <bagasdotme@gmail.com>; 'git' <git@vger.kernel.org>
Cc: 何浩 <hehao@xiaomi.com>; Xin7 Ma 马鑫 <maxin7@xiaomi.com>; 凡军辉 <fanjunhui@xiaomi.com>; 石奉兵 <shifengbing@xiaomi.com>
Subject: RE: RE: [External Mail]Re: Git fork process infinitely and never stop
To be a supplement.
If I delete .git/objects/info/commit-graph, everything works well As well as fetch with `-c core.commitGraph=false`
-----Original Message-----
From: 程洋
Sent: Thursday, July 7, 2022 10:20 PM
To: 'lilinchao@oschina.cn' <lilinchao@oschina.cn>; 'Bagas Sanjaya' <bagasdotme@gmail.com>; 'git' <git@vger.kernel.org>
Cc: 何浩 <hehao@xiaomi.com>; Xin7 Ma 马鑫 <maxin7@xiaomi.com>; 凡军辉 <fanjunhui@xiaomi.com>; 石奉兵 <shifengbing@xiaomi.com>
Subject: RE: RE: [External Mail]Re: Git fork process infinitely and never stop
I found another thing.
1. if I execute `git fetch --filter=blob:none --quiet --progress miui --prune --tags +refs/heads/*:refs/remotes/miui/* +refs/heads/miui13-s-thor-vendor-stable:refs/remotes/miui/miui13-s-thor-vendor-stable` on version 2.25.1. It just throw error rather than infinite loop, like this youtube video "https://www.youtube.com/watch?v=qvYTvVRE0FU&feature=youtu.be"
2. I found if I delete .git/objects, everything goes fine. And there are only 20 files inside it. So I delete them one by one to see which cause the problem. It's `.git/objects/info/commit-graph`. So I upload the file as attachment
Tree before I do second experiment
.
├── 20
│ └── 740928c988ed93daf943869621290d68f62b47
├── 25
│ └── cbb5f02bbcde2effebba84bbc866a29e68afdf
├── 36
│ └── 3aa2d25b71c5aff9d0d8ad8207bc27b4492e8b
├── 5b
│ └── 7b5cb8dd63be48e1466c9d957420a9765a805e
├── 65
│ └── e272c21f28fa8e28dd904f3576f5f23cdb8214
├── 8b
│ └── 148aa56b7c559e217bd31a16e886b16e21cde1
├── 97
│ └── faebca644ae8bfebcbdc8a1dd8e179e9b657de
├── a3
│ └── 852cda2af632dcc7dfbe466d6d8608c2e06520
├── a4
│ └── aa8ae78300217b0da0ab7c4b8ea22b5b74b958
├── a9
│ ├── 04e09d1ee0e0b89acd5196326399d89de70742
│ └── 7d1ffa5c4dad081469b356d0571d0b6166d00e
├── b3
│ └── 2b750166e2d54b8bd3ac62d7aeaf732e14f20d
├── b8
│ └── 957799c3a460ba2e0d26ce0081a4d092dcfb17
├── c5
│ └── be026b3b87a1ae4321700ee45ffcb5eee3ca48
├── d1
│ └── e65d268d5a2230d1d869d55497e0c1eb59b9a5
├── dd
│ └── 483c3c475117275bbf7768a940962842bd5aeb
├── e2
│ └── 6899458dc6cf2c3749c0732ac5b04ccd4c7765
├── e3
│ └── 06b12e22c7914ff80374b7857ee67864a61ba5
├── e7
│ └── a0cc17f9939b80b135c0ec389cbcc98aea70c7
├── eb
│ └── 9169a0d2124594e92720fc6ac1ce3fb29c7d87
├── ed
│ └── 6a815060f960032ecaf70fefdbdae4ac466314
├── f8
│ └── 4401972a0a7020aef85b83561d70af41962a6f
├── info
│ ├── commit-graph
│ └── packs
└── pack
├── pack-029d08823bd8a8eab510ad6ac75c823cfd3ed31e.idx
├── pack-029d08823bd8a8eab510ad6ac75c823cfd3ed31e.pack
├── pack-029d08823bd8a8eab510ad6ac75c823cfd3ed31e.promisor
├── pack-c931093ae6c9df5d36b773f94efc38d9d4b39108.idx
├── pack-c931093ae6c9df5d36b773f94efc38d9d4b39108.pack
├── pack-c931093ae6c9df5d36b773f94efc38d9d4b39108.promisor
├── tmp_idx_RRo8oo
└── tmp_pack_1hgueq
-----------------------------------------------------------------------------------Original Message---------------------------------------------------------------------------------------------------------------------------------------
From: 程洋
Sent: Wednesday, July 6, 2022 10:03 PM
To: lilinchao@oschina.cn; Bagas Sanjaya <bagasdotme@gmail.com>; git <git@vger.kernel.org>
Cc: 何浩 <hehao@xiaomi.com>; Xin7 Ma 马鑫 <maxin7@xiaomi.com>
Subject: 回复: RE: [External Mail]Re: Git fork process infinitely and never stop
To lilinchao:
>So the repo "git/gerrit" is hosted in your local? and how you "copy" it to your own PC?
1. git/gerrit is hosted on remote server
2. I just scp the whole repository of the user who reproduce the problem to our own PC. And then we can reproduce it on our own PC.
To Johannes:
> Hooks may also play a role.
We do have some hooks. But I don't think they're related. Because even I delete those hooks, the problem stands still
To Ævar Arnfjörð:
>I assume you can't share the repo, but perhaps try if you can reproduce it with a "git fast-export --anonymize" version of it, and if so whether you'd be willing to share that. It will publish the "shape of the history" of the repo, but not any meaningful data (all commits, trees, blobs etc. are replaced).
`git fast-export --anonymize` just output is empty. If I try `git fast-export --anonymize --all`, it seems to fetch first, which goes into the infinite loop again
>The YouTube video shows that you're using various options to git-fetch,
>including filters, refspecs etc. Does a plain "git fetch" reproduce
>this, and if not what's the option (try adding them one at a time &
>experiment) that needs to be added to trigger this?
`git fetch` also has this problem.
I somewhat suspect some --filter funny business, but that's just a hunch...
It seems to happen after I told my team to use "partial-clone" AND "git v2.36.1". I'm not sure which one is the cause or both of them cause this.
#/******本邮件及其附件含有小米公司的保密信息,仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本邮件! This e-mail and its attachments contain confidential information from XIAOMI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!******/#
next prev parent reply other threads:[~2022-07-08 10:46 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
2022-07-06 14:03 ` 回复: " 程洋
[not found] ` <11f76b2382934edcb97eb201f0a78a67@xiaomi.com>
2022-07-07 17:54 ` 程洋
2022-07-08 10:45 ` 程洋 [this message]
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=bd33fa6079c2485fb6ee741be05d3f7e@xiaomi.com \
--to=chengyang@xiaomi.com \
--cc=bagasdotme@gmail.com \
--cc=fanjunhui@xiaomi.com \
--cc=git@vger.kernel.org \
--cc=hehao@xiaomi.com \
--cc=lilinchao@oschina.cn \
--cc=maxin7@xiaomi.com \
--cc=shifengbing@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).