From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] SHA-1 collision and venti
Date: Sun, 26 Feb 2017 11:46:18 -0800 [thread overview]
Message-ID: <20170226194618.E3E5F124AEA5@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Sun, 26 Feb 2017 18:25:34 GMT." <CAOw7k5hfR7T1RSuGMQ3i1kd72yr60LXXgD5amuBd9E9gEm_GAw@mail.gmail.com>
On Sun, 26 Feb 2017 18:25:34 GMT Charles Forsyth <charles.forsyth@gmail.com> wrote:
>
> It's curious that svn "corrupts" the repository, if that's really what they
> mean, when two leaf files collide.
> An index or directory colliding with a file would be more understandable.
The only known collision is for files. I suspect this was seen
as a "can't happen" event so may be dealing with the error was
not done right. You can read the report:
https://bugs.webkit.org/show_bug.cgi?id=168774
> > Venti detects a collision on the attempt to write the second copy if that
> > differs from the earlier one stored (error "store collision"). The earlier
> > copy is untouched (venti anyway is write-once per score).
Good to know at least it /detects/ score collisions.
The concern would be that one of two colliding files *can't*
be archived and it will be lost. We only have one example
so it is not a big deal right now.
> > Fossil doesn't handle it well, because it turns up during archiving and
> > ends up marking the archive attempt as failed, but it will try again.
> > Meanwhile, you've got time to change fossil to check the venti error
> > return for "score collision" and announce it, loudly, discarding the second
> > one.
Hopefully the two versions can co-exist on fossil?
> > Obviously if you care about something, make sure your version is in venti
> > first! Chances are that collisions arise from naughty people tricking you
> > later. Probably.
Or may be you are doing research on collsions?!
next prev parent reply other threads:[~2017-02-26 19:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 17:25 Bakul Shah
2017-02-26 17:30 ` Jules Merit
2017-02-26 18:29 ` Charles Forsyth
2017-02-26 18:16 ` Charles Forsyth
2017-02-26 18:25 ` Charles Forsyth
2017-02-26 19:46 ` Bakul Shah [this message]
2017-02-26 21:02 ` Kim Shrier
2017-02-27 15:46 ` Dave MacFarlane
2017-02-27 16:47 ` Charles Forsyth
2017-02-27 17:07 ` Charles Forsyth
2017-02-27 17:28 ` Bakul Shah
2017-02-27 18:14 ` hiro
2017-02-27 18:20 ` Bakul Shah
2017-02-27 18:30 ` Charles Forsyth
2017-02-27 19:02 ` Charles Forsyth
2017-02-27 20:05 ` cinap_lenrek
2017-02-27 20:14 ` Bakul Shah
2017-02-27 21:12 ` Riddler
2017-02-27 22:20 ` Charles Forsyth
2017-03-01 12:21 ` erik quanstrom
2017-03-01 12:35 ` David du Colombier
2017-02-27 19:34 ` Skip Tavakkolian
2017-02-26 18:48 ` Bakul Shah
2017-02-26 19:57 ` Charles Forsyth
2017-02-26 20:06 ` Jadon Bennett
2017-02-26 20:16 ` Bakul Shah
2017-02-28 15:47 Darren Wise
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=20170226194618.E3E5F124AEA5@mail.bitblocks.com \
--to=bakul@bitblocks.com \
--cc=9fans@9fans.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.
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 NNTP newsgroup(s).