From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Glen Choo via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, Taylor Blau <me@ttaylorr.com>,
Glen Choo <chooglen@google.com>
Subject: Re: [PATCH] object-file: use real paths when adding alternates
Date: Thu, 17 Nov 2022 20:41:44 +0100 [thread overview]
Message-ID: <221117.86h6yxgy7b.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <Y3aBzbzub7flQyca@coredump.intra.peff.net>
On Thu, Nov 17 2022, Jeff King wrote:
> On Thu, Nov 17, 2022 at 05:31:13PM +0000, Glen Choo via GitGitGadget wrote:
> [...]
>> @@ -596,7 +603,7 @@ static void link_alt_odb_entries(struct repository *r, const char *alt,
>> return;
>> }
>>
>> - strbuf_add_absolute_path(&objdirbuf, r->objects->odb->path);
>> + strbuf_realpath(&objdirbuf, r->objects->odb->path, 1);
>> if (strbuf_normalize_path(&objdirbuf) < 0)
>> die(_("unable to normalize object directory: %s"),
>> objdirbuf.buf);
>
> Similarly here, I think we'd want to _replace_ the normalize with a
> realpath. There's no point in doing both. It's OK to die in this one
> because we assume the object directory can be normalized/realpath'd.
>
> So I'd have expected the code portion of your patch to be more like:
>
> diff --git a/object-file.c b/object-file.c
> index 957790098f..c6a195c6dd 100644
> --- a/object-file.c
> +++ b/object-file.c
> @@ -508,6 +508,7 @@ static int link_alt_odb_entry(struct repository *r, const struct strbuf *entry,
> {
> struct object_directory *ent;
> struct strbuf pathbuf = STRBUF_INIT;
> + struct strbuf tmp = STRBUF_INIT;
> khiter_t pos;
>
> if (!is_absolute_path(entry->buf) && relative_base) {
> @@ -516,12 +517,18 @@ static int link_alt_odb_entry(struct repository *r, const struct strbuf *entry,
> }
> strbuf_addbuf(&pathbuf, entry);
>
> - if (strbuf_normalize_path(&pathbuf) < 0 && relative_base) {
> - error(_("unable to normalize alternate object path: %s"),
> - pathbuf.buf);
> - strbuf_release(&pathbuf);
> - return -1;
> + if (!strbuf_realpath(&tmp, pathbuf.buf, 0)) {
> + if (relative_base) {
> + error(_("unable to normalize alternate object path: %s"),
> + pathbuf.buf);
> + strbuf_release(&pathbuf);
> + return -1;
> + }
> + /* allow broken paths from env per 37a95862c625 */
> + strbuf_addstr(&tmp, pathbuf.buf);
> }
> + strbuf_swap(&pathbuf, &tmp);
> + strbuf_release(&tmp);
>
> /*
> * The trailing slash after the directory name is given by
> @@ -596,10 +603,7 @@ static void link_alt_odb_entries(struct repository *r, const char *alt,
> return;
> }
>
> - strbuf_add_absolute_path(&objdirbuf, r->objects->odb->path);
> - if (strbuf_normalize_path(&objdirbuf) < 0)
> - die(_("unable to normalize object directory: %s"),
> - objdirbuf.buf);
> + strbuf_realpath(&objdirbuf, r->objects->odb->path, 1);
>
> while (*alt) {
> alt = parse_alt_odb_entry(alt, sep, &entry);
>
> The "tmp" swapping in link_alt_odb_entry is kind of unfortunate. It
> would be nice if there were an in-place version of strbuf_realpath, even
> if it was using two buffers under the hood (which is how the normalize
> code does it). And then the patch really would be s/normalize/realpath/,
> which is easier to understand.
>
> Possibly this should also be using the "forgiving" version. We
> eventually error out on missing entries later on, so it's not a big deal
> to error here. But it would let us keep the error message the same. I
> don't know that it matters much in practice.
This probably isn't worth it, but I wondered if this wouldn't be easier
if we pulled that memory management into the caller, it's not
performance sensitive (or maybe, how many alternatives do people have
:)), but an advantage of this is that we avoid the free()/malloc() if we
only get partway through, i.e. return early and keep looping.
In terms of general code smell & how we manage the "return" here, as
adding "RESULT_MUST_BE_USED" to this shows we never use the "0" or "-1"
(or any other...) return value.
That's been the case since this was added in c2f493a4ae1 (Transitively
read alternatives, 2006-05-07), so we can probably just make this a
"void" and ditch the returns if we're finding ourselves juggling these
return values...
object-file.c | 44 ++++++++++++++++++++++----------------------
1 file changed, 22 insertions(+), 22 deletions(-)
diff --git a/object-file.c b/object-file.c
index c6a195c6dd2..1a94d98e0c7 100644
--- a/object-file.c
+++ b/object-file.c
@@ -504,47 +504,43 @@ static void read_info_alternates(struct repository *r,
const char *relative_base,
int depth);
static int link_alt_odb_entry(struct repository *r, const struct strbuf *entry,
- const char *relative_base, int depth, const char *normalized_objdir)
+ const char *relative_base, int depth,
+ const char *normalized_objdir,
+ struct strbuf *pathbuf)
{
struct object_directory *ent;
- struct strbuf pathbuf = STRBUF_INIT;
struct strbuf tmp = STRBUF_INIT;
khiter_t pos;
if (!is_absolute_path(entry->buf) && relative_base) {
- strbuf_realpath(&pathbuf, relative_base, 1);
- strbuf_addch(&pathbuf, '/');
+ strbuf_realpath(pathbuf, relative_base, 1);
+ strbuf_addch(pathbuf, '/');
}
- strbuf_addbuf(&pathbuf, entry);
+ strbuf_addbuf(pathbuf, entry);
- if (!strbuf_realpath(&tmp, pathbuf.buf, 0)) {
- if (relative_base) {
- error(_("unable to normalize alternate object path: %s"),
- pathbuf.buf);
- strbuf_release(&pathbuf);
- return -1;
- }
+ if (!strbuf_realpath(&tmp, pathbuf->buf, 0)) {
+ if (relative_base)
+ return error(_("unable to normalize alternate object path: %s"),
+ pathbuf->buf);
/* allow broken paths from env per 37a95862c625 */
- strbuf_addstr(&tmp, pathbuf.buf);
+ strbuf_addstr(&tmp, pathbuf->buf);
}
- strbuf_swap(&pathbuf, &tmp);
+ strbuf_swap(pathbuf, &tmp);
strbuf_release(&tmp);
/*
* The trailing slash after the directory name is given by
* this function at the end. Remove duplicates.
*/
- while (pathbuf.len && pathbuf.buf[pathbuf.len - 1] == '/')
- strbuf_setlen(&pathbuf, pathbuf.len - 1);
+ while (pathbuf->len && pathbuf->buf[pathbuf->len - 1] == '/')
+ strbuf_setlen(pathbuf, pathbuf->len - 1);
- if (!alt_odb_usable(r->objects, &pathbuf, normalized_objdir, &pos)) {
- strbuf_release(&pathbuf);
+ if (!alt_odb_usable(r->objects, pathbuf, normalized_objdir, &pos))
return -1;
- }
CALLOC_ARRAY(ent, 1);
- /* pathbuf.buf is already in r->objects->odb_by_path */
- ent->path = strbuf_detach(&pathbuf, NULL);
+ /* pathbuf->buf is already in r->objects->odb_by_path */
+ ent->path = strbuf_detach(pathbuf, NULL);
/* add the alternate entry */
*r->objects->odb_tail = ent;
@@ -593,6 +589,7 @@ static void link_alt_odb_entries(struct repository *r, const char *alt,
{
struct strbuf objdirbuf = STRBUF_INIT;
struct strbuf entry = STRBUF_INIT;
+ struct strbuf pathbuf = STRBUF_INIT;
if (!alt || !*alt)
return;
@@ -610,8 +607,11 @@ static void link_alt_odb_entries(struct repository *r, const char *alt,
if (!entry.len)
continue;
link_alt_odb_entry(r, &entry,
- relative_base, depth, objdirbuf.buf);
+ relative_base, depth, objdirbuf.buf,
+ &pathbuf);
+ strbuf_reset(&pathbuf);
}
+ strbuf_release(&pathbuf);
strbuf_release(&entry);
strbuf_release(&objdirbuf);
}
next prev parent reply other threads:[~2022-11-17 19:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 17:31 [PATCH] object-file: use real paths when adding alternates Glen Choo via GitGitGadget
2022-11-17 18:47 ` Jeff King
2022-11-17 19:41 ` Ævar Arnfjörð Bjarmason [this message]
2022-11-17 21:57 ` Jeff King
2022-11-17 22:03 ` Taylor Blau
2022-11-18 0:00 ` Glen Choo
2022-11-17 21:54 ` Taylor Blau
2022-11-21 23:49 ` [PATCH v2] " Glen Choo via GitGitGadget
2022-11-22 0:56 ` Ævar Arnfjörð Bjarmason
2022-11-22 19:53 ` Jeff King
2022-11-24 0:50 ` Glen Choo
2022-11-24 1:06 ` Jeff King
2022-11-24 0:20 ` Glen Choo
2022-11-22 19:40 ` Jeff King
2022-11-24 0:55 ` [PATCH v3] " Glen Choo via GitGitGadget
2022-11-24 1:08 ` Jeff King
2022-11-25 6:51 ` 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=221117.86h6yxgy7b.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=chooglen@google.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
/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).