Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Mon, 29 Mar 2021 07:18:09 -0700
From:   Richard Cochran <richardcochran@gmail.com>
To:     Daphne Preston-Kendal <dpk@nonceword.org>
Cc:     Miroslav Lichvar <mlichvar@redhat.com>,
        Thomas Gleixner <tglx@linutronix.de>,
        LKML <linux-kernel@vger.kernel.org>,
        John Stultz <john.stultz@linaro.org>,
        "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Subject: Re: [Bug 212265] New: clock_gettime(CLOCK_TAI, ...) should return an
 error when TAI has not been configured
Message-ID: <20210329141809.GA20909@hoboy.vegasvil.org>
References: <YGGbAIoCKDbZLQQ0@localhost>
 <2505F20D-ED84-4B36-9504-8A8C756C992E@nonceword.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2505F20D-ED84-4B36-9504-8A8C756C992E@nonceword.org>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On Mon, Mar 29, 2021 at 11:56:31AM +0200, Daphne Preston-Kendal wrote:
> > The other is that the kernel updates the offset when a leap
> > second is inserted/deleted even if the original offset is zero, so
> > checking for zero (in the kernel or an application) works only until
> > the first leap second after boot.
> 
> This is a problem and definitely speaks for having a way to tell whether CLOCK_TAI has been set up at all.

+1

Thanks,
Richard