From: Junio C Hamano <gitster@pobox.com>
To: Han-Wen Nienhuys <hanwen@google.com>
Cc: sunshine@sunshineco.com, jrn@google.com, git@vger.kernel.org
Subject: Re: [PATCH v7 1/1] sideband: highlight keywords in remote sideband output
Date: Fri, 17 Aug 2018 11:33:06 -0700 [thread overview]
Message-ID: <xmqqd0ugc07x.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20180807125108.104293-2-hanwen@google.com> (Han-Wen Nienhuys's message of "Tue, 7 Aug 2018 14:51:08 +0200")
Han-Wen Nienhuys <hanwen@google.com> writes:
> +/*
> + * Optionally highlight one keyword in remote output if it appears at the start
> + * of the line. This should be called for a single line only, which is
> + * passed as the first N characters of the SRC array.
> + */
> +static void maybe_colorize_sideband(struct strbuf *dest, const char *src, int n)
> +{
> + int i;
> +
> + if (!want_color_stderr(use_sideband_colors())) {
> + strbuf_add(dest, src, n);
> + return;
> + }
> +
> + while (isspace(*src)) {
> + strbuf_addch(dest, *src);
> + src++;
> + n--;
> + }
This loop can run out of bytes in src in search of non-space before
n gets to zero or negative, and when that happens ...
> + for (i = 0; i < ARRAY_SIZE(keywords); i++) {
> + struct keyword_entry *p = keywords + i;
> + int len = strlen(p->keyword);
> + /*
> + * Match case insensitively, so we colorize output from existing
> + * servers regardless of the case that they use for their
> + * messages. We only highlight the word precisely, so
> + * "successful" stays uncolored.
> + */
> + if (!strncasecmp(p->keyword, src, len) && !isalnum(src[len])) {
... these access src[] beyond the end of what the caller intended to
show us, and also ...
> + strbuf_addstr(dest, p->color);
> + strbuf_add(dest, src, len);
> + strbuf_addstr(dest, GIT_COLOR_RESET);
> + n -= len;
> + src += len;
> + break;
> + }
> + }
> +
> + strbuf_add(dest, src, n);
... this will now try to add 0 or negative number of bytes.
> +
> +}
> +
Perhaps this will help (not really tested). The second hunk is an
unrelated style clean-up.
sideband.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/sideband.c b/sideband.c
index 1c6bb0e25b..d99a559a44 100644
--- a/sideband.c
+++ b/sideband.c
@@ -75,11 +75,13 @@ static void maybe_colorize_sideband(struct strbuf *dest, const char *src, int n)
return;
}
- while (isspace(*src)) {
+ while (isspace(*src) && n) {
strbuf_addch(dest, *src);
src++;
n--;
}
+ if (!n)
+ return;
for (i = 0; i < ARRAY_SIZE(keywords); i++) {
struct keyword_entry *p = keywords + i;
@@ -101,7 +103,6 @@ static void maybe_colorize_sideband(struct strbuf *dest, const char *src, int n)
}
strbuf_add(dest, src, n);
-
}
next prev parent reply other threads:[~2018-08-17 18:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 12:51 [PATCH v7 0/1] sideband: highlight keywords in remote sideband output Han-Wen Nienhuys
2018-08-07 12:51 ` [PATCH v7 1/1] " Han-Wen Nienhuys
2018-08-17 18:33 ` Junio C Hamano [this message]
2018-08-17 18:44 ` Re* " Junio C Hamano
2018-08-18 6:09 ` Jonathan Nieder
2018-08-18 14:40 ` Junio C Hamano
2018-08-18 16:02 ` Junio C Hamano
2018-08-18 16:16 ` Junio C Hamano
2018-08-18 23:22 ` Jeff King
2018-08-20 14:21 ` Junio C Hamano
2018-08-20 12:21 ` Han-Wen Nienhuys
2018-08-20 12:21 ` Han-Wen Nienhuys
2018-08-20 14:32 ` Junio C Hamano
2018-08-18 6:35 ` Jonathan Nieder
2018-08-18 16:06 ` Junio C Hamano
2018-08-07 21:01 ` [PATCH v7 0/1] " Junio C Hamano
2018-08-08 13:12 ` Han-Wen Nienhuys
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=xmqqd0ugc07x.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=hanwen@google.com \
--cc=jrn@google.com \
--cc=sunshine@sunshineco.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).