From: "René Scharfe" <l.s.r@web.de>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2018, #04; Thu, 20)
Date: Mon, 1 Oct 2018 23:37:29 +0200 [thread overview]
Message-ID: <bf40fe3e-20f5-456b-b800-b655a2aadb4d@web.de> (raw)
In-Reply-To: <20181001201202.GA10234@sigill.intra.peff.net>
Am 01.10.2018 um 22:12 schrieb Jeff King:
> On Mon, Oct 01, 2018 at 09:16:07PM +0200, René Scharfe wrote:
>
>> Am 21.09.2018 um 07:22 schrieb Junio C Hamano:
>>> * cc/delta-islands (2018-08-16) 7 commits
>> [...]
>>> * jk/pack-delta-reuse-with-bitmap (2018-08-21) 6 commits
>>
>> Not sure if it's the interaction of the two topics or if only one of
>> them is to blame, but the result of the merge can dereference a NULL
>> pointer. Found using Clang's UBSan and t5310.
>>
>> Here's a patch that avoids the issue, but I don't know if it's the
>> right thing to do -- should we rather treat a non-existing base as
>> "not from the same island" instead?
>>
>> And it's certainly ugly -- that condition is complicated enough
>> already. Splitting it up in a nice way would probably help, but how?
>
> Perhaps like in 2fa233a554 (pack-objects: handle island check for
> "external" delta base, 2018-09-18)?
Perhaps indeed. ;-) That patch looks exactly like the fix I wished for,
and then some. I'm just not fully sure about the added branch for the
combination of the two features, because I don't know either of them in
depth.
René
prev parent reply other threads:[~2018-10-01 21:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 5:22 What's cooking in git.git (Sep 2018, #04; Thu, 20) Junio C Hamano
2018-09-21 14:30 ` Segfault in master due to 4fbcca4eff Ævar Arnfjörð Bjarmason
2018-09-21 14:34 ` Derrick Stolee
2018-09-21 14:40 ` Ævar Arnfjörð Bjarmason
2018-09-21 14:53 ` Derrick Stolee
2018-09-21 15:55 ` Junio C Hamano
2018-09-21 23:37 ` Ævar Arnfjörð Bjarmason
2018-09-21 23:45 ` Jeff King
2018-09-21 23:49 ` Ævar Arnfjörð Bjarmason
2018-09-21 17:05 ` What's cooking in git.git (Sep 2018, #04; Thu, 20) Johannes Sixt
2018-09-21 17:17 ` Junio C Hamano
2018-09-23 21:39 ` Paul-Sebastian Ungureanu
2018-10-01 19:16 ` René Scharfe
2018-10-01 20:12 ` Jeff King
2018-10-01 21:37 ` René Scharfe [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
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=bf40fe3e-20f5-456b-b800-b655a2aadb4d@web.de \
--to=l.s.r@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).