public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 221186] clock_gettime CLOCK_TAI is incorrectly specified
Date: Sat, 07 Mar 2026 14:56:32 +0000	[thread overview]
Message-ID: <bug-221186-11311-suuU8DZ6Ke@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221186-11311@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=221186

--- Comment #1 from Alejandro Colomar (alx@kernel.org) ---
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

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  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
2026-03-07 20:59   ` Paul Eggert
2026-03-07 22:44     ` Alejandro Colomar
2026-03-07 14:56 ` bugzilla-daemon [this message]
2026-03-07 20:59 ` [Bug 221186] " 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=bug-221186-11311-suuU8DZ6Ke@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --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