All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Florian Schmidt <flosch@nutanix.com>
Cc: git@vger.kernel.org,
	 Jonathan Davies <jonathan.davies@nutanix.com>,
	Phillip Wood <phillip.wood@dunelm.org.uk>,
	 Denton Liu <liu.denton@gmail.com>,
	Linus Arver <linusa@google.com>
Subject: Re: [PATCH] wt-status: Don't find scissors line beyond buf len
Date: Thu, 07 Mar 2024 11:20:11 -0800	[thread overview]
Message-ID: <xmqq34t1n91w.fsf@gitster.g> (raw)
In-Reply-To: <20240307183743.219951-1-flosch@nutanix.com> (Florian Schmidt's message of "Thu, 7 Mar 2024 18:37:38 +0000")

Florian Schmidt <flosch@nutanix.com> writes:

> Currently, if
> (a) There is a "---" divider in a commit message,
> (b) At some point beyond that divider, there is a cut-line (that is,
>     "# ------------------------ >8 ------------------------") in the
>     commit message,
> (c) the user does not explicitly set the "no-divider" option,
> then "git interpret-trailers" will hang indefinitively.

You do not have to say "Currently, if"; just "If" is sufficient.
Cf. Documentation/SubmittingPatches[[present-tense]]

> This is because when (a) is true, find_end_of_log_message() will invoke
> ignored_log_message_bytes() with a len that is intended to make it
> ignore the part of the commit message beyond the divider. However,
> ignored_log_message_bytes() calls wt_status_locate_end(), and that
> function ignores the length restriction when it tries to locate the cut
> line. If it manages to find one, the returned cutoff value is greater
> than len. At this point, ignored_log_message_bytes() goes into an
> infinite loop, because it won't advance the string parsing beyond len,
> but the exit condition expects to reach cutoff.

Good finding.  

> It seems sensible to expect that wt_status_locate_end() should honour
> the length parameter passed in, and doing so fixes this issue.

Thanks.  This is an ancient bug, not a retression from recent
changes to the trailer library [linusa CC'ed to save him from
wasting his time wondering if he broke anything].

> diff --git a/wt-status.c b/wt-status.c
> index b5a29083df..51a84575ed 100644
> --- a/wt-status.c
> +++ b/wt-status.c
> @@ -1089,14 +1089,19 @@ size_t wt_status_locate_end(const char *s, size_t len)
>  {
>  	const char *p;
>  	struct strbuf pattern = STRBUF_INIT;
> +	size_t result = len;
>  
>  	strbuf_addf(&pattern, "\n%c %s", comment_line_char, cut_line);
>  	if (starts_with(s, pattern.buf + 1))
> -		len = 0;
> -	else if ((p = strstr(s, pattern.buf)))
> -		len = p - s + 1;
> +		result = 0;
> +	else if ((p = strstr(s, pattern.buf))) {
> +		result = p - s + 1;
> +		if (result > len) {
> +			result = len;
> +		}
> +	}
>  	strbuf_release(&pattern);
> -	return len;
> +	return result;
>  }

Looks correct, but we probably can make the fix a lot more isolated
into a single block, like the attached patch.  How does this look?

 wt-status.c | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git c/wt-status.c w/wt-status.c
index b5a29083df..511f37cfe0 100644
--- c/wt-status.c
+++ w/wt-status.c
@@ -1093,8 +1093,11 @@ size_t wt_status_locate_end(const char *s, size_t len)
 	strbuf_addf(&pattern, "\n%c %s", comment_line_char, cut_line);
 	if (starts_with(s, pattern.buf + 1))
 		len = 0;
-	else if ((p = strstr(s, pattern.buf)))
-		len = p - s + 1;
+	else if ((p = strstr(s, pattern.buf))) {
+		int newlen = p - s + 1;
+		if (newlen < len)
+			len = newlen;
+	}
 	strbuf_release(&pattern);
 	return len;
 }

  reply	other threads:[~2024-03-07 19:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07 18:37 [PATCH] wt-status: Don't find scissors line beyond buf len Florian Schmidt
2024-03-07 19:20 ` Junio C Hamano [this message]
2024-03-07 20:47   ` Junio C Hamano
2024-03-07 21:09     ` Eric Sunshine
2024-03-07 21:15     ` Kristoffer Haugsbakk
2024-03-07 21:24       ` Junio C Hamano
2024-03-07 21:26         ` Eric Sunshine
2024-03-07 21:30           ` Kristoffer Haugsbakk
2024-03-08  9:08   ` Florian Schmidt
2024-03-08 15:26     ` Junio C Hamano
2024-03-08 17:43       ` Florian Schmidt
2024-04-06  1:37   ` Linus Arver
2024-03-07 19:35 ` Junio C Hamano
2024-03-08  9:13   ` Florian Schmidt

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=xmqq34t1n91w.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=flosch@nutanix.com \
    --cc=git@vger.kernel.org \
    --cc=jonathan.davies@nutanix.com \
    --cc=linusa@google.com \
    --cc=liu.denton@gmail.com \
    --cc=phillip.wood@dunelm.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.