From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: git@vger.kernel.org, Derrick Stolee <derrickstolee@github.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 6/6] sequencer: fail early if invalid ref is given to 'update-ref' instruction
Date: Fri, 30 Sep 2022 19:09:04 +0200 [thread overview]
Message-ID: <220930.86a66gvkse.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <20220930140948.80367-7-szeder.dev@gmail.com>
On Fri, Sep 30 2022, SZEDER Gábor wrote:
> + if (item->command == TODO_UPDATE_REF) {
> + struct strbuf ref = STRBUF_INIT;
> + int ret = 0;
> +
> + item->commit = NULL;
> + item->arg_offset = bol - buf;
> + item->arg_len = (int)(eol - bol);
> +
> + strbuf_add(&ref, bol, item->arg_len);
Just a nit and maybe not worth it, but we've done this allocation dance
just because..
> + if (!starts_with(ref.buf, "refs/") ||
> + check_refname_format(ref.buf, 0))
...there isn't such a thing as checkn_refname_format() taking a "size_t
len" or whatever.
So maybe not worth it, but if we do the equivalent of:
static checkn_refname_format(const char *refname, size_t len, unsigned int flags)
{
struct strbuf ref = STRBUF_INIT;
int ret;
strbuf_add(&ref, refname, len);
ret = check_refname_format(ref,buf, flags);
strbuf_release(&ref);
return ret;
}
This caller could just (untested):
if (!starts_with(bol, "refs/") ||
checkn_refname_format(bol, eol - bol, 0))
return error(_("...%.*s", item->arg_len, bol));
Which saves us the copy in case the "starts_with" test is all we need.
Even without such a helper, maybe:
int bad;
[...]
bad = (!starts_with(ref.buf, "refs/") ||
check_refname_format(ref.buf, 0));
strbuf_release(&buf);
if (bad)
return error(_("...%.*s", item->arg_len, bol));
return 0;
Would make it clearer that the strbuf is just for the use of
check_refname_format().
What you have already is also fine, this just sent me down a rabbit hole
of re-learning that most of the string duplication we do for
check_refname_format() could be avoided if it was slightly less stupid,
i.e. accepted a "len" and "prefix" (i.e. "pretend your refname argument
started with 'refs/heads/'", or whatever).
> + ret = error(_("invalid ref for update-ref instruction: %s"), ref.buf);
> +
> + strbuf_release(&ref);
> + return ret;
> + }
> +
> end_of_object_name = (char *) bol + strcspn(bol, " \t\n");
> saved = *end_of_object_name;
> *end_of_object_name = '\0';
> diff --git a/t/t3404-rebase-interactive.sh b/t/t3404-rebase-interactive.sh
> index 2e081b3914..b97f1e8b31 100755
> --- a/t/t3404-rebase-interactive.sh
> +++ b/t/t3404-rebase-interactive.sh
> @@ -1964,6 +1964,34 @@ test_expect_success 'respect user edits to update-ref steps' '
> test_cmp_rev HEAD refs/heads/no-conflict-branch
> '
>
> +test_expect_success 'update-refs with invalid refs' '
> + cat >fake-todo-4 <<-EOF &&
> + update-ref refs/heads/foo..bar
> + update-ref refs/heads/foo.lock
> + update-ref foo
> + update-ref foo/bar
> + pick $(git rev-parse HEAD)
Another potentially hidden segfault/exit code for "git"
next prev parent reply other threads:[~2022-09-30 17:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 14:09 [PATCH 0/6] rebase --update-refs: smooth out some rough edges SZEDER Gábor
2022-09-30 14:09 ` [PATCH 1/6] t2407-worktree-heads.sh: remove outdated loop SZEDER Gábor
2022-09-30 14:09 ` [PATCH 2/6] t3404-rebase-interactive: mark a test with REFFILES prereq SZEDER Gábor
2022-09-30 16:46 ` Ævar Arnfjörð Bjarmason
2022-10-05 16:45 ` Junio C Hamano
2022-09-30 14:09 ` [PATCH 3/6] rebase -i: emphasize that 'update-ref' expects a fully-qualified ref SZEDER Gábor
2022-09-30 14:09 ` [PATCH 4/6] sequencer: avoid empty lines after 'update-ref' instructions SZEDER Gábor
2022-09-30 17:18 ` Derrick Stolee
2022-10-05 16:49 ` Junio C Hamano
2022-09-30 14:09 ` [PATCH 5/6] sequencer: duplicate the result of resolve_ref_unsafe() SZEDER Gábor
2022-09-30 16:45 ` Ævar Arnfjörð Bjarmason
2022-09-30 16:51 ` Ævar Arnfjörð Bjarmason
2022-09-30 17:23 ` Derrick Stolee
2022-10-09 17:23 ` SZEDER Gábor
2022-09-30 14:09 ` [PATCH 6/6] sequencer: fail early if invalid ref is given to 'update-ref' instruction SZEDER Gábor
2022-09-30 17:09 ` Ævar Arnfjörð Bjarmason [this message]
2022-09-30 17:29 ` [PATCH 0/6] rebase --update-refs: smooth out some rough edges Derrick Stolee
2022-10-01 16:31 ` SZEDER Gábor
2022-10-01 16:53 ` Junio C Hamano
2022-10-05 17:14 ` 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:
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=220930.86a66gvkse.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=szeder.dev@gmail.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 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.