git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thiago Farina <tfransosi@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] setup_revisions(): take pathspec from command line and --stdin correctly
Date: Wed, 11 May 2011 19:00:36 -0300	[thread overview]
Message-ID: <BANLkTin401CWZntHowyCw=Ua0+SNAZ7m7A@mail.gmail.com> (raw)
In-Reply-To: <7vd3jogbe0.fsf@alter.siamese.dyndns.org>

On Wed, May 11, 2011 at 6:44 PM, Junio C Hamano <gitster@pobox.com> wrote:
> When the command line has "--" disambiguator, we take the remainder of
> argv[] as "prune_data", but when --stdin is given at the same time, we
> need to append to the existing prune_data and end up attempting to
> realloc(3) it, which would not work and can lead to a segfault or worse.
>
> Fix it by consistently using append_prune_data() throughout the input
> processing.  Also avoid counting the number of existing paths in the
> function over and over again.
>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
>
>  * This is relative to 1.6.6; the bug originates back to 60da8b1 (Make
>   --stdin option to "log" family read also pathspecs, 2009-11-20).
>
>  revision.c                |   80 ++++++++++++++++-----------------------------
>  t/t6017-rev-list-stdin.sh |   17 +++++++++
>  2 files changed, 45 insertions(+), 52 deletions(-)
>
> diff --git a/revision.c b/revision.c
> index c92ffc2..58b5651 100644
> --- a/revision.c
> +++ b/revision.c
> @@ -956,35 +956,34 @@ int handle_revision_arg(const char *arg, struct rev_info *revs,
>        return 0;
>  }
>
> -static void read_pathspec_from_stdin(struct rev_info *revs, struct strbuf *sb, const char ***prune_data)
> -{
> -       const char **prune = *prune_data;
> -       int prune_nr;
> -       int prune_alloc;
> +struct cmdline_pathspec {
Maybe prune_data_pathspec?

> +       int alloc;
> +       int nr;
> +       const char **path;
> +};
>
> -       /* count existing ones */
> -       if (!prune)
> -               prune_nr = 0;
> -       else
> -               for (prune_nr = 0; prune[prune_nr]; prune_nr++)
> -                       ;
> -       prune_alloc = prune_nr; /* not really, but we do not know */
> +static void append_prune_data(struct cmdline_pathspec *prune, const char **av)
av is the same thing as argv? If so, is it worth naming it argv? I
know the old was av, so maybe not though.

> +{
> +       while (*av) {
> +               ALLOC_GROW(prune->path, prune->nr+1, prune->alloc);
I'd add spaces between prune->nr + 1. But I think is fine as is too.

> +               prune->path[prune->nr++] = *(av++);
> +       }
> +}
>
> +static void read_pathspec_from_stdin(struct rev_info *revs, struct strbuf *sb,
> +                                    struct cmdline_pathspec *prune)
> +{
>        while (strbuf_getwholeline(sb, stdin, '\n') != EOF) {
>                int len = sb->len;
>                if (len && sb->buf[len - 1] == '\n')
>                        sb->buf[--len] = '\0';
> -               ALLOC_GROW(prune, prune_nr+1, prune_alloc);
> -               prune[prune_nr++] = xstrdup(sb->buf);
> +               ALLOC_GROW(prune->path, prune->nr+1, prune->alloc);
> +               prune->path[prune->nr++] = xstrdup(sb->buf);
>        }
> -       if (prune) {
> -               ALLOC_GROW(prune, prune_nr+1, prune_alloc);
> -               prune[prune_nr] = NULL;
> -       }
> -       *prune_data = prune;
>  }
>
> -static void read_revisions_from_stdin(struct rev_info *revs, const char ***prune)
> +static void read_revisions_from_stdin(struct rev_info *revs,
> +                                     struct cmdline_pathspec *prune)
>  {
>        struct strbuf sb;
>        int seen_dashdash = 0;
> @@ -1279,34 +1278,6 @@ static int for_each_good_bisect_ref(each_ref_fn fn, void *cb_data)
>        return for_each_ref_in("refs/bisect/good", fn, cb_data);
>  }
>
> -static void append_prune_data(const char ***prune_data, const char **av)
> -{
> -       const char **prune = *prune_data;
> -       int prune_nr;
> -       int prune_alloc;
> -
> -       if (!prune) {
> -               *prune_data = av;
> -               return;
> -       }
> -
> -       /* count existing ones */
> -       for (prune_nr = 0; prune[prune_nr]; prune_nr++)
> -               ;
> -       prune_alloc = prune_nr; /* not really, but we do not know */
> -
> -       while (*av) {
> -               ALLOC_GROW(prune, prune_nr+1, prune_alloc);
> -               prune[prune_nr++] = *av;
> -               av++;
> -       }
> -       if (prune) {
> -               ALLOC_GROW(prune, prune_nr+1, prune_alloc);
> -               prune[prune_nr] = NULL;
> -       }
> -       *prune_data = prune;
> -}
> -
>  /*
>  * Parse revision information, filling in the "rev_info" structure,
>  * and removing the used arguments from the argument list.
> @@ -1317,7 +1288,9 @@ static void append_prune_data(const char ***prune_data, const char **av)
>  int setup_revisions(int argc, const char **argv, struct rev_info *revs, const char *def)
>  {
>        int i, flags, left, seen_dashdash, read_from_stdin;
> -       const char **prune_data = NULL;
> +       struct cmdline_pathspec prune_data;
> +
> +       memset(&prune_data, 0, sizeof(prune_data));
>
>        /* First, search for "--" */
>        seen_dashdash = 0;
> @@ -1328,7 +1301,7 @@ int setup_revisions(int argc, const char **argv, struct rev_info *revs, const ch
>                argv[i] = NULL;
>                argc = i;
>                if (argv[i + 1])
> -                       prune_data = argv + i + 1;
> +                       append_prune_data(&prune_data, argv + i + 1);
>                seen_dashdash = 1;
>                break;
>        }
> @@ -1420,8 +1393,11 @@ int setup_revisions(int argc, const char **argv, struct rev_info *revs, const ch
>                }
>        }
>
> -       if (prune_data)
> -               revs->prune_data = get_pathspec(revs->prefix, prune_data);
> +       if (prune_data.nr) {
> +               ALLOC_GROW(prune_data.path, prune_data.nr+1, prune_data.alloc);
> +               prune_data.path[prune_data.nr++] = NULL;
> +               revs->prune_data = get_pathspec(revs->prefix, prune_data.path);
> +       }
>
>        if (revs->def == NULL)
>                revs->def = def;
> diff --git a/t/t6017-rev-list-stdin.sh b/t/t6017-rev-list-stdin.sh
> index f1c32db..667b375 100755
> --- a/t/t6017-rev-list-stdin.sh
> +++ b/t/t6017-rev-list-stdin.sh
> @@ -58,4 +58,21 @@ check side-3 ^side-4 -- file-3
>  check side-3 ^side-2
>  check side-3 ^side-2 -- file-1
>
> +test_expect_success 'not only --stdin' '
> +       cat >expect <<-EOF &&
> +       7
> +
> +       file-1
> +       file-2
> +       EOF
> +       cat >input <<-EOF &&
> +       ^master^
> +       --
> +       file-2
> +       EOF
> +       git log --pretty=tformat:%s --name-only --stdin master -- file-1 \
> +               <input >actual &&
> +       test_cmp expect actual
> +'
> +
>  test_done
> --
> 1.7.5.1.315.ge7efa
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

      reply	other threads:[~2011-05-11 22:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-11 21:44 [PATCH] setup_revisions(): take pathspec from command line and --stdin correctly Junio C Hamano
2011-05-11 22:00 ` Thiago Farina [this message]

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='BANLkTin401CWZntHowyCw=Ua0+SNAZ7m7A@mail.gmail.com' \
    --to=tfransosi@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).