From: YONETANI Tomokazu <qhwt+git@les.ath.cx>
To: git@vger.kernel.org
Subject: [PATCH] git-fast-import possible memory corruption problem
Date: Sun, 14 Dec 2008 11:08:22 +0900 [thread overview]
Message-ID: <20081214020822.GB4121@les.ath.cx> (raw)
[-- Attachment #1: Type: text/plain, Size: 919 bytes --]
Hello.
While trying to convert NetBSD CVS repository to Git, I've been
experiencing 100% reproducible crash of git-fast-import. After
poking here and there and I noticed a dubious code fragment in
pool_alloc():
:
r = p->next_free;
/* round out to a 'uintmax_t' alignment */
if (len & (sizeof(uintmax_t) - 1))
len += sizeof(uintmax_t) - (len & (sizeof(uintmax_t) - 1));
p->next_free += len;
return r;
As the `round out' takes place AFTER it found the room in the mem_pool,
there's a small chance of p->next_free being set outside of the chosen
area, up to (sizeof(uintmax_t) - 1) bytes. pool_strdup() is one of the
functions which can trigger the problem, when pool_alloc() finds a room
at the end of a pool entry and the requested length is not multiple of
size(uintmax_t). I believe attached patch addresses this problem.
Best regards,
YONETANI Tomokazu.
[-- Attachment #2: git-fast-import.patch --]
[-- Type: text/plain, Size: 1489 bytes --]
diff --git a/fast-import.c b/fast-import.c
index 3c035a5..fb4367a 100644
--- a/fast-import.c
+++ b/fast-import.c
@@ -549,11 +549,15 @@ static unsigned int hc_str(const char *s, size_t len)
return r;
}
-static void *pool_alloc(size_t len)
+static void *_pool_alloc(size_t len, int zero)
{
struct mem_pool *p;
void *r;
+ /* round out to a 'uintmax_t' alignment */
+ if (len & (sizeof(uintmax_t) - 1))
+ len += sizeof(uintmax_t) - (len & (sizeof(uintmax_t) - 1));
+
for (p = mem_pool; p; p = p->next_pool)
if ((p->end - p->next_free >= len))
break;
@@ -561,7 +565,8 @@ static void *pool_alloc(size_t len)
if (!p) {
if (len >= (mem_pool_alloc/2)) {
total_allocd += len;
- return xmalloc(len);
+ r = xmalloc(len);
+ goto out;
}
total_allocd += sizeof(struct mem_pool) + mem_pool_alloc;
p = xmalloc(sizeof(struct mem_pool) + mem_pool_alloc);
@@ -572,19 +577,22 @@ static void *pool_alloc(size_t len)
}
r = p->next_free;
- /* round out to a 'uintmax_t' alignment */
- if (len & (sizeof(uintmax_t) - 1))
- len += sizeof(uintmax_t) - (len & (sizeof(uintmax_t) - 1));
p->next_free += len;
+out:
+ if (zero)
+ memset(r, 0, len);
return r;
}
+static void *pool_alloc(size_t len)
+{
+ return _pool_alloc(len, 0);
+}
+
static void *pool_calloc(size_t count, size_t size)
{
size_t len = count * size;
- void *r = pool_alloc(len);
- memset(r, 0, len);
- return r;
+ return _pool_alloc(len, 1);
}
static char *pool_strdup(const char *s)
next reply other threads:[~2008-12-14 2:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-14 2:08 YONETANI Tomokazu [this message]
2008-12-14 3:42 ` [PATCH] git-fast-import possible memory corruption problem Junio C Hamano
2008-12-14 5:53 ` Junio C Hamano
2008-12-14 10:45 ` YONETANI Tomokazu
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=20081214020822.GB4121@les.ath.cx \
--to=qhwt+git@les.ath.cx \
--cc=git@vger.kernel.org \
/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).