From: Kiran Rangoon <kiranrangoon0@gmail.com>
To: util-linux@vger.kernel.org
Cc: thomas@t-8ch.de, Kiran Rangoon <kiranrangoon0@gmail.com>
Subject: [PATCH v3 1/2] libuuid: Refactor UUID time conversion for pre-epoch dates
Date: Wed, 17 Dec 2025 15:59:52 -0500 [thread overview]
Message-ID: <20251217205952.10904-1-kiranrangoon0@gmail.com> (raw)
In-Reply-To: <9dc90e33-30e2-48c3-8602-00fce280f9ef@t-8ch.de>
I revised the code in response to your feedback.
> Looking at this more closely: __uuid_time() is directly exposed to users
> of libuuid as uuid_time(). This means that any change of the function's
> contract would break all external users and should be avoided at all
> costs.
Reversed the change there.
> Fortunately it turns out that the timestamps embedded in UUIDs
> only use 60 bits. This means that the calculation can be performed in an
> int64_t without any risk of over- or underflow. Please try to implement
> it that way instead.
I'm using signed int64_t here as suggested.
> It might be useful to change the signature of gregorian_to_unix() to
> "static void gregorian_to_unix(uint64_t ts, struct timeval *tv)".
I revised the code to use a struct timeval now.
> Also please perform each logical step in a dedicated commit.
I made two commits, one for the code change and the other for tests, but
if there is a way you would perfer me to do it I could change it.
---
libuuid/src/uuid_time.c | 25 +++++++++----------------
1 file changed, 9 insertions(+), 16 deletions(-)
diff --git a/libuuid/src/uuid_time.c b/libuuid/src/uuid_time.c
index f0d2c8f36..293fc7e68 100644
--- a/libuuid/src/uuid_time.c
+++ b/libuuid/src/uuid_time.c
@@ -60,34 +60,29 @@
/* prototype to make compiler happy */
time_t __uuid_time(const uuid_t uu, struct timeval *ret_tv);
-static int64_t gregorian_to_unix(uint64_t ts)
+static void gregorian_to_unix(uint64_t ts, struct timeval *tv)
{
- const uint64_t offset = 0x01B21DD213814000ULL;
+ const uint64_t offset = 0x01B21DD213814000ULL;
+ int64_t t = (int64_t) ts - (int64_t) offset;
- if (ts < offset) {
- errno = EOVERFLOW;
- return -1;
- }
-
- return ts - offset;
+ tv->tv_sec = t / 10000000;
+ tv->tv_usec = (t % 10000000) / 10;
}
static void uuid_time_v1(const struct uuid *uuid, struct timeval *tv)
{
uint32_t high;
- int64_t clock_reg;
+ uint64_t clock_reg;
high = uuid->time_mid | ((uuid->time_hi_and_version & 0xFFF) << 16);
clock_reg = uuid->time_low | ((uint64_t) high << 32);
- clock_reg = gregorian_to_unix(clock_reg);
- tv->tv_sec = clock_reg / 10000000;
- tv->tv_usec = (clock_reg % 10000000) / 10;
+ gregorian_to_unix(clock_reg, tv);
}
static void uuid_time_v6(const struct uuid *uuid, struct timeval *tv)
{
- int64_t clock_reg;
+ uint64_t clock_reg;
clock_reg = uuid->time_low;
clock_reg <<= 16;
@@ -95,9 +90,7 @@ static void uuid_time_v6(const struct uuid *uuid, struct timeval *tv)
clock_reg <<= 12;
clock_reg |= uuid->time_hi_and_version & 0xFFF;
- clock_reg = gregorian_to_unix(clock_reg);
- tv->tv_sec = clock_reg / 10000000;
- tv->tv_usec = (clock_reg % 10000000) / 10;
+ gregorian_to_unix(clock_reg, tv);
}
static void uuid_time_v7(const struct uuid *uuid, struct timeval *tv)
--
2.47.3
next prev parent reply other threads:[~2025-12-17 21:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-13 20:04 [PATCH] libuuid: Fix pre-1970 UUID v1 timestamp wraparound Kiran Rangoon
2025-12-13 23:36 ` Thomas Weißschuh
2025-12-14 1:01 ` [PATCH v2] " Kiran Rangoon
2025-12-16 13:08 ` Thomas Weißschuh
2025-12-16 20:40 ` Kiran
2025-12-16 23:21 ` Thomas Weißschuh
2025-12-17 20:42 ` [PATCH v3 1/2] libuuid: Refactor UUID time conversion for pre-epoch dates Kiran Rangoon
2025-12-17 20:59 ` Kiran Rangoon [this message]
2025-12-18 21:31 ` Kiran Rangoon
2025-12-19 11:40 ` Thomas Weißschuh
2025-12-23 18:00 ` [PATCH v4 0/4] libuuid: Fix pre-1970 UUID timestamp overflow Kiran Rangoon
2025-12-23 18:00 ` [PATCH v4 1/4] libuuid: simplify gregorian-to-unix offset calculation Kiran Rangoon
2025-12-23 18:00 ` [PATCH v4 2/4] libuuid: refactor gregorian_to_unix to populate timeval directly Kiran Rangoon
2025-12-23 18:03 ` [PATCH v4 1/4] libuuid: simplify gregorian-to-unix offset calculation Kiran Rangoon
2025-12-23 18:22 ` [PATCH v4 0/4] libuuid: Fix pre-1970 UUID timestamp overflow Thomas Weißschuh
2025-12-28 8:47 ` Thomas Weißschuh
2025-12-23 18:04 ` [PATCH v4 3/4] libuuid: fix timestamp overflow for pre-1970 dates Kiran Rangoon
2025-12-23 18:05 ` [PATCH v4 4/4] tests: correct UUID timestamp test expectations Kiran Rangoon
2025-12-17 11:01 ` [PATCH v2] libuuid: Fix pre-1970 UUID v1 timestamp wraparound Karel Zak
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=20251217205952.10904-1-kiranrangoon0@gmail.com \
--to=kiranrangoon0@gmail.com \
--cc=thomas@t-8ch.de \
--cc=util-linux@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