From: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Jens Lehmann" <Jens.Lehmann@web.de>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: [PATCH 3/7] sha1_file: refuse to write commits referring to external objects
Date: Thu, 24 Jan 2013 15:42:16 +0700 [thread overview]
Message-ID: <1359016940-18849-3-git-send-email-pclouds@gmail.com> (raw)
In-Reply-To: <1359016940-18849-1-git-send-email-pclouds@gmail.com>
Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
---
sha1_file.c | 34 ++++++++++++++++++++++++++++++++++
1 file changed, 34 insertions(+)
diff --git a/sha1_file.c b/sha1_file.c
index af71122..5948dcb 100644
--- a/sha1_file.c
+++ b/sha1_file.c
@@ -2615,12 +2615,46 @@ static int write_loose_object(const unsigned char *sha1, char *hdr, int hdrlen,
return move_temp_to_file(tmp_file, filename);
}
+static void check_sha1_file_for_external_source(const char *buf,
+ unsigned long len,
+ const char *type)
+{
+ struct object_info oi;
+ unsigned char sha1[20];
+
+ /*
+ * It is assumed that the object is well formatted. Otherwise
+ * die() is waiting..
+ */
+ if (!strcmp(type, "commit")) {
+ const char *tail = buf + len;
+ if (get_sha1_hex(buf + 5, sha1) < 0 ||
+ sha1_object_info_extended(sha1, &oi) != OBJ_TREE ||
+ (oi.alt && oi.alt->external))
+ die("cannot create a commit with external tree %s",
+ sha1_to_hex(sha1));
+ buf += 46; /* "tree " + "hex sha1" + "\n" */
+
+ while (buf + 48 < tail && !memcmp(buf, "parent ", 7)) {
+ if (get_sha1_hex(buf + 7, sha1) < 0 ||
+ sha1_object_info_extended(sha1, &oi) != OBJ_COMMIT ||
+ (oi.alt && oi.alt->external))
+ die("cannot create a commit with external parent %s",
+ sha1_to_hex(sha1));
+ buf += 48; /* "parent " + hex sha1 + "\n" */
+ }
+ }
+}
+
int write_sha1_file(const void *buf, unsigned long len, const char *type, unsigned char *returnsha1)
{
unsigned char sha1[20];
char hdr[32];
int hdrlen;
+ if (object_database_contaminated)
+ check_sha1_file_for_external_source(buf, len, type);
+
/* Normally if we have it in the pack then we do not bother writing
* it out into .git/objects/??/?{38} file.
*/
--
1.8.0.rc3.18.g0d9b108
next prev parent reply other threads:[~2013-01-24 8:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 8:42 [PATCH 1/7] sha1_file: keep track of where an SHA-1 object comes from Nguyễn Thái Ngọc Duy
2013-01-24 8:42 ` [PATCH 2/7] sha1_file: separate alt object db from own repos and submodules's Nguyễn Thái Ngọc Duy
2013-01-24 8:42 ` Nguyễn Thái Ngọc Duy [this message]
2013-01-24 8:42 ` [PATCH 4/7] sha1_file: refuse to write trees referring to external objects Nguyễn Thái Ngọc Duy
2013-01-24 8:42 ` [PATCH 5/7] sha1_file: refuse to write tags " Nguyễn Thái Ngọc Duy
2013-01-24 8:42 ` [PATCH 6/7] read-cache: refuse to create index " Nguyễn Thái Ngọc Duy
2013-01-24 19:15 ` Junio C Hamano
2013-01-25 2:00 ` Duy Nguyen
2013-01-25 19:00 ` Junio C Hamano
2013-01-28 5:48 ` Duy Nguyen
2013-01-28 5:54 ` Junio C Hamano
2013-01-28 5:57 ` Duy Nguyen
2013-01-28 6:06 ` Junio C Hamano
2013-01-28 6:18 ` Duy Nguyen
2013-01-28 6:36 ` Junio C Hamano
2013-01-28 6:57 ` Duy Nguyen
2013-01-24 8:42 ` [PATCH 7/7] refs: do not update ref(log) " Nguyễn Thái Ngọc Duy
2013-01-24 17:45 ` [PATCH 1/7] sha1_file: keep track of where an SHA-1 object comes from Junio C Hamano
2013-01-25 1:38 ` Duy Nguyen
2013-01-25 3:58 ` Junio C Hamano
2013-01-25 4:02 ` Duy Nguyen
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=1359016940-18849-3-git-send-email-pclouds@gmail.com \
--to=pclouds@gmail.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).