From: Alejandro Colomar <alx@kernel.org>
To: bugzilla-daemon@kernel.org
Cc: linux-man@vger.kernel.org, Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: [Bug 221186] New: clock_gettime CLOCK_TAI is incorrectly specified
Date: Sat, 7 Mar 2026 15:56:28 +0100 [thread overview]
Message-ID: <aaw8SLhwjSGR0X4m@devuan> (raw)
In-Reply-To: <bug-221186-11311@https.bugzilla.kernel.org/>
[-- Attachment #1: Type: text/plain, Size: 1912 bytes --]
Hi,
On 2026-03-07T14:21:17+0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=221186
>
> Bug ID: 221186
> Summary: clock_gettime CLOCK_TAI is incorrectly specified
> Product: Documentation
> Version: unspecified
> Hardware: All
> OS: Linux
> Status: NEW
> Severity: normal
> Priority: P3
> Component: man-pages
> Assignee: documentation_man-pages@kernel-bugs.osdl.org
> Reporter: mpatocka@redhat.com
> Regression: No
>
> The man page for clock_gettime says "CLOCK_TAI (since Linux 3.10;
> Linux-specific)
> A nonsettable system-wide clock derived from wall-clock time but ignoring leap
> seconds."
>
> When UTC was announced, it was already 10 seconds behind TAI. Since that, 27
> leap seconds have been added. According to the man page, the difference between
> wall clock an CLOCK_TAI should be 27 seconds, but in it is 37 seconds in fact.
> The kernel is correct (it returns 37 as the difference between TAI and UTC),
> but the man page should be fixed to reflect that.
>
> I suggest to change the man page to:
>
> CLOCK_TAI (since Linux 3.10; Linux-specific)
> A nonsettable system-wide clock showing physical time elapsed since Jan 1 1970
> 0:00:00.00 TAI (Dec 31 1969 23:59:50.00 UTC). This clock does not experience
> discontinuities and backwards jumps caused by NTP inserting leap seconds as
> CLOCK_REALTIME does. This clock changes when system time is adjusted by the
> user or NTP for the purpose of correcting wrong time setting. TAI means temps
> atomique international (International Atomic Time).
Would you mind sending a patch?
BTW, Paul, would you mind reviewing this bug report and suggestion?
Have a lovely day!
Alex
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-03-07 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 14:21 [Bug 221186] New: clock_gettime CLOCK_TAI is incorrectly specified bugzilla-daemon
2026-03-07 14:56 ` Alejandro Colomar [this message]
2026-03-07 20:59 ` Paul Eggert
2026-03-07 22:44 ` Alejandro Colomar
2026-03-07 14:56 ` [Bug 221186] " bugzilla-daemon
2026-03-07 20:59 ` bugzilla-daemon
2026-03-07 22:45 ` bugzilla-daemon
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=aaw8SLhwjSGR0X4m@devuan \
--to=alx@kernel.org \
--cc=bugzilla-daemon@kernel.org \
--cc=eggert@cs.ucla.edu \
--cc=linux-man@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