From: Christian Couder <chriscool@tuxfamily.org>
To: Junio C Hamano <gitster@pobox.com>, Stephen Boyd <bebarino@gmail.com>
Cc: git@vger.kernel.org
Subject: [PATCH] log-tree: fix patch filename computation in "git format-patch"
Date: Fri, 27 Mar 2009 01:13:01 +0100 [thread overview]
Message-ID: <20090327011301.a5185805.chriscool@tuxfamily.org> (raw)
When using "git format-patch", "get_patch_filename" in
"log-tree.c" calls "strbuf_splice" that could die with
the following message:
"`pos + len' is too far after the end of the buffer"
if you have:
buf->len < start_len + FORMAT_PATCH_NAME_MAX
but:
buf->len + suffix_len > start_len + FORMAT_PATCH_NAME_MAX
This patch tries to get rid of that bug.
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
---
log-tree.c | 11 ++++++-----
1 files changed, 6 insertions(+), 5 deletions(-)
This bug happens on "pu".
diff --git a/log-tree.c b/log-tree.c
index 56a3488..ade79ab 100644
--- a/log-tree.c
+++ b/log-tree.c
@@ -187,16 +187,17 @@ void get_patch_filename(struct commit *commit, int nr, const char *suffix,
strbuf_addf(buf, commit ? "%04d-" : "%d", nr);
if (commit) {
+ int max_len = start_len + FORMAT_PATCH_NAME_MAX;
format_commit_message(commit, "%f", buf, DATE_NORMAL);
/*
* Replace characters at the end with the suffix if the
* filename is too long
*/
- if (buf->len + suffix_len > FORMAT_PATCH_NAME_MAX + start_len)
- strbuf_splice(buf,
- start_len + FORMAT_PATCH_NAME_MAX - suffix_len,
- suffix_len, suffix, suffix_len);
- else
+ if (buf->len + suffix_len > max_len) {
+ int base = (max_len > buf->len) ? buf->len : max_len;
+ strbuf_splice(buf, base - suffix_len, suffix_len,
+ suffix, suffix_len);
+ } else
strbuf_addstr(buf, suffix);
}
}
--
1.6.2.1.506.g7aa09
next reply other threads:[~2009-03-27 0:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 0:13 Christian Couder [this message]
2009-03-27 4:15 ` [PATCH] log-tree: fix patch filename computation in "git format-patch" Junio C Hamano
2009-03-27 4:31 ` Stephen Boyd
2009-03-27 7:15 ` Christian Couder
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=20090327011301.a5185805.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=bebarino@gmail.com \
--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).