From: Victoria Dye <vdye@github.com>
To: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Jeff King <peff@peff.net>,
Phillip Wood <phillip.wood123@gmail.com>
Subject: Re: What's cooking in git.git (Sep 2022, #08; Tue, 27)
Date: Tue, 27 Sep 2022 18:52:02 -0700 [thread overview]
Message-ID: <be8f11f2-c4ad-0542-066b-3bbc99a16dae@github.com> (raw)
In-Reply-To: <xmqqtu4s1q1m.fsf@gitster.g>
Junio C Hamano wrote:
> * vd/fix-unaligned-read-index-v4 (2022-09-23) 1 commit
> - read-cache: avoid misaligned reads in index v4
>
> The codepath that reads from the index v4 had unaligned memory
> accesses, which has been corrected.
>
> Expecting a reroll.
> cf. <Yy4nkEnhuzt2iH+R@coredump.intra.peff.net>
> cf. <bb3a2470-7ff5-e4a6-040a-96e0e3833978@gmail.com>
> source: <pull.1366.git.1663962236069.gitgitgadget@gmail.com>
>
How drastic an update were you expecting for this re-roll? To keep the fix
minimal (that is, focused on 'create_from_disk()'), I was planning to just
add some comments explaining the implementation (in response to [1]). If the
goal is to get this merged quickly, I'd want to avoid a larger refactor
(suggested in [2] & [3]), since doing so would either make the
implementations of "read from disk" ('create_from_disk()') and "write to
disk" ('copy_cache_entry_to_ondisk()') different/difficult to compare, or
would involve a more invasive refactor to update both functions [4].
However, if there's no time pressure (after all, this bug has existed since
the introduction of index v4!), I'm happy to do that refactor. It would
expand the series to 2 or 3 patches, but should address all of the
suggestions made so far and make the code overall a bit clearer.
Let me know what you think!
Thanks,
- Victoria
[1] https://lore.kernel.org/git/bb3a2470-7ff5-e4a6-040a-96e0e3833978@gmail.com/
[2] https://lore.kernel.org/git/Yy4nkEnhuzt2iH+R@coredump.intra.peff.net/
[3] https://lore.kernel.org/git/YzH+IPFBGleIsAUe@coredump.intra.peff.net/
[4] https://lore.kernel.org/git/e5954e90-6b5c-46a6-0842-b3d7d1e06b33@github.com/
next prev parent reply other threads:[~2022-09-28 1:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 21:11 What's cooking in git.git (Sep 2022, #08; Tue, 27) Junio C Hamano
2022-09-28 1:52 ` Victoria Dye [this message]
2022-09-28 4:18 ` vd/fix-unaligned-read-index-v4, was " Jeff King
2022-09-28 4:19 ` [PATCH 1/3] pack-bitmap: make read_be32() public Jeff King
2022-09-28 4:21 ` [PATCH 2/3] read-cache: read on-disk entries in byte order Jeff King
2022-09-29 11:27 ` Jeff King
2022-09-29 15:47 ` Junio C Hamano
2022-09-28 4:23 ` [PATCH 3/3] read-cache: use read_be32() in create_from_disk() Jeff King
2022-09-28 16:41 ` vd/fix-unaligned-read-index-v4, was Re: What's cooking in git.git (Sep 2022, #08; Tue, 27) Junio C Hamano
2022-09-28 17:01 ` Ævar Arnfjörð Bjarmason
2022-09-28 17:41 ` 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=be8f11f2-c4ad-0542-066b-3bbc99a16dae@github.com \
--to=vdye@github.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=phillip.wood123@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.