mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Eric Sunshine <>
To: Lars Kellogg-Stedman <>
Subject: Re: [PATCH v2] line-range: Fix infinite loop bug with degenerate regex
Date: Tue, 6 Dec 2022 23:33:23 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, Dec 5, 2022 at 2:45 PM Lars Kellogg-Stedman <> wrote:
> line-range: Fix infinite loop bug with degenerate regex


> When the -L argument to "git log" is passed the degenerate regular
> expression "$" (as in "-L :$:line-range.c"), this results in an
> infinite loop in find_funcname_matching_regexp() (the function
> iterates through the file correctly, but when it reaches the end of
> the file it matches $ against the empty string, "", and at that points
> loops forever).


> Modify the loop condition from while (1) to while (*start) so that the
> loop exits when start is the empty string. In this case, "git log" exits
> with the error:
>     fatal: -L parameter '$' starting at line 1: no match

I've never really used `-L:funcname:`, so it took me by surprise that
this would be reported as a fatal error. However, now that I've read
through the code and put a bit of thought into degenerate cases, I
can't come up with any better way to report it. Okay.

> Originally reported in <>.
> Signed-off-by: Lars Kellogg-Stedman <>
> ---
> diff --git a/line-range.c b/line-range.c
> @@ -135,7 +135,7 @@ static const char *find_funcname_matching_regexp(xdemitconf_t *xecfg, const char
>  {
>         int reg_error;
>         regmatch_t match[1];
> -       while (1) {
> +       while (*start) {
>                 const char *bol, *eol;
>                 reg_error = regexec(regexp, start, 1, match, 0);
>                 if (reg_error == REG_NOMATCH)
> @@ -161,6 +161,8 @@ static const char *find_funcname_matching_regexp(xdemitconf_t *xecfg, const char
>                         return bol;
>                 start = eol;
>         }
> +
> +    return NULL;
>  }

I'm not particularly familiar with this code (even though I touched it
years ago), so I can't say whether this is the best fix, but it seems
reasonable now that I've studied the code and put some thought into
degenerate cases. I had wondered if it would be possible to catch
these degenerate cases in some general way, but whatever ideas I had
seemed too special-purpose; your solution here is straightforward and
probably more robust than special-purpose code.

Style-wise, I'd probably drop the blank line before `return NULL`.

Please do re-roll once more with a test which verifies that this bug
has been fixed. Here's a test you can add to the bottom of
t/ for that purpose (be sure to re-indent it with
TABs which Gmail mushes out):

    test_expect_success 'degenerate -L:$: does not hang' '
        >content-immaterial &&
        git add content-immaterial &&
        git commit -m immaterial &&
        test_must_fail git log -L:$:content-immaterial

And here's my sign-off which you can insert above your own sign-off if
you include the above test.

    Signed-off-by: Eric Sunshine <>

  reply	other threads:[~2022-12-07  4:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-05 19:36 [PATCH v2] line-range: Fix infinite loop bug with degenerate regex Lars Kellogg-Stedman
2022-12-07  4:33 ` Eric Sunshine [this message]
2022-12-07  4:52 ` Ævar Arnfjörð Bjarmason
2022-12-07  5:29   ` Junio C Hamano
2022-12-07 20:30   ` SZEDER Gábor
2022-12-09 19:16   ` Lars Kellogg-Stedman
2022-12-11  1:53 ` [PATCH v3] line-range: Fix infinite loop bug with degenerate '$' regex Lars Kellogg-Stedman
2022-12-11  3:32   ` Junio C Hamano
2022-12-11  3:34     ` Junio C Hamano
2022-12-14 14:53     ` Lars Kellogg-Stedman
2022-12-18  1:33       ` Junio C Hamano
2022-12-19 22:48 ` [PATCH v4] line-range: fix infinite loop bug with " Lars Kellogg-Stedman
2022-12-19 22:55   ` Ævar Arnfjörð Bjarmason
2022-12-20  0:00     ` Eric Sunshine
2022-12-20  1:07       ` Junio C Hamano

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 read-only IMAP folder(s) and NNTP newsgroup(s).