From: Jeff King <peff@peff.net>
To: Jeffrey Walton <noloader@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: disabling sha1dc unaligned access, was Re: One failed self test on Fedora 29
Date: Mon, 11 Mar 2019 14:19:04 -0400 [thread overview]
Message-ID: <20190311181904.GA16865@sigill.intra.peff.net> (raw)
In-Reply-To: <CAH8yC8=9HOAmDE93aXd300kOJSOa0sA8Qv2cNn2M-EO-gqiktw@mail.gmail.com>
On Mon, Mar 11, 2019 at 06:40:21AM -0400, Jeffrey Walton wrote:
> > So anyway, I think this needs a patch to the upstream sha1dc project.
>
> https://github.com/cr-marcstevens/sha1collisiondetection/issues/47
Thanks, it looks like the turnaround on that may be pretty quick. Once
it's merged there, we'll need a local patch to bump the gitlink sha1 and
tweak the Makefile.
-Peff
next prev parent reply other threads:[~2019-03-11 18:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 10:48 One failed self test on Fedora 29 Jeffrey Walton
2019-03-08 17:43 ` Todd Zullinger
2019-03-09 12:34 ` Jeffrey Walton
2019-03-09 13:12 ` Jeffrey Walton
2019-03-11 2:00 ` Junio C Hamano
2019-03-11 2:16 ` Jeffrey Walton
2019-03-11 3:37 ` disabling sha1dc unaligned access, was " Jeff King
2019-03-11 10:40 ` Jeffrey Walton
2019-03-11 18:19 ` Jeff King [this message]
2019-03-11 11:58 ` Duy Nguyen
2019-03-11 18:15 ` Thomas Braun
2019-03-11 18:23 ` Jeff King
2019-03-12 7:27 ` Junio C Hamano
2019-03-12 10:51 ` Jeff King
2019-03-13 11:47 ` Thomas Braun
2019-03-13 15:39 ` Jeff King
2019-03-13 16:00 ` Ævar Arnfjörð Bjarmason
2019-03-12 8:53 ` Ævar Arnfjörð Bjarmason
2019-03-12 11:05 ` Jeff King
2019-03-12 12:09 ` Ævar Arnfjörð Bjarmason
2019-03-12 21:01 ` Jeff King
2019-03-12 21:06 ` [PATCH] Makefile: fix unaligned loads in sha1dc with UBSan Jeff King
2019-03-12 21:17 ` Ævar Arnfjörð Bjarmason
2019-03-12 21:19 ` Jeff King
2019-03-11 3:29 ` One failed self test on Fedora 29 Jeff King
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=20190311181904.GA16865@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=noloader@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.
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).