From: Jeff King <peff@peff.net>
To: Davide Berardi <davide.berardi6@unibo.it>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH v2] clone: Don't segfault on -b specifing a non-commit
Date: Mon, 4 Nov 2019 23:37:49 -0500 [thread overview]
Message-ID: <20191105043749.GA27601@sigill.intra.peff.net> (raw)
In-Reply-To: <20191103180716.GA72007@carpenter.lan>
On Sun, Nov 03, 2019 at 06:07:18PM +0000, Davide Berardi wrote:
> -static void update_head(const struct ref *our, const struct ref *remote,
> +static struct commit *lookup_commit_helper(const struct ref *our,
> + const struct ref *remote,
> + const char *msg, int *err)
> +{
> + const struct object_id *tip = NULL;
> + struct commit *tip_commit = NULL;
> +
> + if (our)
> + tip = &our->old_oid;
> + else if (remote)
> + tip = &remote->old_oid;
> +
> + if (!tip)
> + return NULL;
> +
> + tip_commit = lookup_commit_reference_gently_err(the_repository, tip, 1, err);
> + if (!tip_commit) {
> + /*
> + * The given non-commit cannot be checked out,
> + * so have a 'master' branch and leave it unborn.
> + */
> + warning(_("non-commit cannot be checked out"));
> + create_symref("HEAD", "refs/heads/master", msg);
> + return NULL;
> + }
> +
> + return tip_commit;
> +}
I like the logic flow in this function, which is IMHO clearer than the
existing code. But the "err" thing puzzled me for a moment. I think you
are trying to tell the difference between the case that both "our" and
"remote" are NULL, and the case that we saw a non-commit. In either case
we return NULL, but only one is an error.
But:
- I don't think that logic needs to extend down into
lookup_commit_reference_gently(); a NULL return from it would always
be an error, wouldn't it?
- we could probably simplify this by just inlining it into
update_head(). Something like:
if (our)
tip = &our->old_oid;
else if (remote)
tip = &remote->old_oid;
if (!tip) {
/*
* We have no local branch requested with "-b", and the
* remote HEAD is unborn. There's nothing to update HEAD
* to, but this state is not an error.
*/
return 0;
}
tip_commit = lookup_commit_reference_gently(...);
if (!tip_commit) {
/*
* The given non-commit cannot be checked out, etc...
*/
warning(...);
create_symref(...);
return -1;
}
...and then existing code to use tip_commit...
/*
* we'd always return 0 here, because our update_ref calls die on
* error
*/
return 0;
> @@ -1268,8 +1303,10 @@ int cmd_clone(int argc, const char **argv, const char *prefix)
> }
>
> junk_mode = JUNK_LEAVE_REPO;
> - fetch_if_missing = 1;
> - err = checkout(submodule_progress);
> + if (!err) {
> + fetch_if_missing = 1;
> + err = checkout(submodule_progress);
> + }
This part makes sense. We might want an explanatory comment along the
lines of:
/*
* Only try to checkout if we successfully updated HEAD; otherwise
* HEAD isn't pointing to the thing the user wanted.
/
if (!err) {
...
> -struct commit *lookup_commit_reference_gently(struct repository *r,
> - const struct object_id *oid, int quiet)
> +struct commit *lookup_commit_reference_gently_err(struct repository *r,
> + const struct object_id *oid, int quiet, int *err)
And this part I think could just go away, if you take my suggestion
above.
> diff --git a/t/t5609-clone-branch.sh b/t/t5609-clone-branch.sh
> index 6e7a7be052..d57f750eeb 100755
> --- a/t/t5609-clone-branch.sh
> +++ b/t/t5609-clone-branch.sh
> @@ -20,7 +20,10 @@ test_expect_success 'setup' '
> echo one >file && git add file && git commit -m one &&
> git checkout -b two &&
> echo two >file && git add file && git commit -m two &&
> - git checkout master) &&
> + git checkout master &&
> + blob=$(git rev-parse HEAD:file) &&
> + echo $blob > .git/refs/heads/broken-tag &&
> + echo $blob > .git/refs/heads/broken-head) &&
Minor style nit, but we usually avoid the space after ">".
> +test_expect_success 'clone -b with a non-commit tag must fallback' '
> + test_must_fail git clone -b broken-tag parent clone-broken-tag &&
> + (cd clone-broken-tag &&
> + check_HEAD master)
> +'
> +test_expect_success 'clone -b with a non-commit head must fallback' '
> + test_must_fail git clone -b broken-head parent clone-broken-head &&
> + (cd clone-broken-head &&
> + check_HEAD master)
> +'
OK, this second one covers the first conditional from update_head():
if (our && skip_prefix(our->name, "refs/heads/", &head)) {
and the first one covers the second conditional:
} else if (our) {
Should we cover the third conditional, too?
I think it would be the case that the remote HEAD is pointing to a
non-commit (since that's a corrupt repository, it might make sense
create a separate sub-repository).
-Peff
next prev parent reply other threads:[~2019-11-05 4:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 0:24 [PATCH] Segmentation Fault on non-commit --branch clone Davide Berardi
2019-11-01 19:08 ` Johannes Schindelin
2019-11-01 19:35 ` Jeff King
2019-11-02 10:16 ` Junio C Hamano
2019-11-03 18:16 ` Davide Berardi
2019-11-04 3:55 ` Junio C Hamano
2019-11-02 9:18 ` Junio C Hamano
2019-11-01 19:43 ` Jeff King
2019-11-02 10:07 ` Junio C Hamano
2019-11-03 18:07 ` [PATCH v2] clone: Don't segfault on -b specifing a non-commit Davide Berardi
2019-11-05 4:37 ` Jeff King [this message]
2019-11-06 1:36 ` Junio C Hamano
2019-11-06 4:05 ` Jeff King
2019-11-06 9:53 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191105043749.GA27601@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=davide.berardi6@unibo.it \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).