c104ea8f180db4be2b491ef5b1f2626958dce80d |
|
07-Jun-2017 |
Josef 'Jeff' Sipek <jeff.sipek@dovecot.fi> |
lib: guid_128_generate() needs to correctly convert usecs to nsecs
The timestamp in the guid starts off with real time, but "runs ahead" if a lot
of guids are generated. If not many guids are being generated, the timestamp
is fast-forwarded to the current ioloop_timeval. The buggy comparison prevented
fast forwarding when tv_sec matched, but tv_nsec value was > 0 (which
was true most of the time). |
5b02d2191f2dd9da567c70b383243395ec0ce13d |
|
07-May-2016 |
Martti Rannanjärvi <martti.rannanjarvi@dovecot.fi> |
lib: Fixed potential collision in guid_generate()
There wasn't enough padding for tv_nsec and it was also assuming 16 bit
PIDs. Because of these there was a tiny possibility of two
guid_generate() calls returning the same GUID.
This changes the GUID format a bit, but it was used only by sdbox code,
which doesn't assume anything about the GUID format. |
c1684fd2affe6159e99bc6de0fd387ce802f0ca6 |
|
29-Apr-2016 |
Timo Sirainen <timo.sirainen@dovecot.fi> |
lib: Set timestamp part more accurately in guid_128_generate()
Previously a long-running process would keep the timestamp close to its
original start time. This doesn't really matter as long as GUIDs are treated
opaque, but some pieces of code prefer to try to use the timestamp fields
since they're already there. This makes such code work more nicely. |
efaa1272c1b682bc2e105b2f374152a6a1f45825 |
|
25-Nov-2014 |
Phil Carmody <phil@dovecot.fi> |
lib: guid - turn uint8_t * parameters into guid_128_t
As we expose the type's internals, there's no concrete difference between
the two, but it might help static code checkers to detect misuse of the
library, or sloppy typing.
Signed-off-by: Phil Carmody <phil@dovecot.fi> |