From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: davids@webmaster.com
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Time-based RFC 4122 UUID generator
Date: Mon, 19 Nov 2007 22:58:49 +0000 [thread overview]
Message-ID: <20071119225849.4cbb7e37@the-village.bc.nu> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKCECCIFAC.davids@webmaster.com>
> Any UUID generator that can produce duplicate UUIDs with probability
> significantly less than purely random UUIDs is so badly broken that it
> should not ever be used. Anyone who finds such a UUID generator should
> immediately either fix it or throw it on the junk heap. Anyone who knowingly
> uses such a UUID generator should be publically shamed.
That depends what they are using it for. Deliberately colliding with
other UUIDs is sometimes highly desirable, just not usually in productive
circles.
next prev parent reply other threads:[~2007-11-19 23:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-18 19:38 Helge Deller
2007-11-18 21:05 ` Andrew Morton
2007-11-18 21:34 ` Sam Ravnborg
2007-11-18 21:43 ` Helge Deller
2007-11-19 21:56 ` David Schwartz
2007-11-19 22:58 ` Alan Cox [this message]
2007-11-20 6:44 ` H. Peter Anvin
2007-11-20 22:58 ` Helge Deller
2007-11-21 0:20 ` Alan Cox
2007-11-18 21:40 ` Helge Deller
2007-11-20 6:31 ` Matt Mackall
2007-11-20 21:59 ` Helge Deller
2007-11-20 22:55 ` Matt Mackall
2007-11-20 23:11 ` Helge Deller
2007-11-20 23:34 ` Matt Mackall
2007-11-20 23:00 ` Theodore Tso
2007-11-20 23:30 ` Helge Deller
2007-12-10 5:36 ` [e2fsprogs PATCH] Userspace solution to time-based UUID without duplicates Theodore Tso
2007-12-16 21:53 ` Helge Deller
2007-12-17 0:07 ` Theodore Tso
2007-11-20 6:15 ` [PATCH] Time-based RFC 4122 UUID generator Andrew Morton
2007-11-20 22:40 ` Helge Deller
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=20071119225849.4cbb7e37@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®