From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Kuwahara,T." <6vvetjsrt26xsrzlh1z0zn4d2grdah@gmail.com> Subject: Re: [PATCH V8 02/13] ntp: add ADJ_SETOFFSET mode bit Date: Thu, 13 Jan 2011 05:39:04 +0900 Message-ID: References: <20110108175028.GA22308@riccoc20.at.omicron.at> <1294678145.3068.6.camel@work-vm> <1294693597.3068.12.camel@work-vm> <1294779309.3441.66.camel@work-vm> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <1294779309.3441.66.camel@work-vm> Sender: linux-kernel-owner@vger.kernel.org To: john stultz Cc: Richard Cochran , linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, netdev@vger.kernel.org, Alan Cox , Arnd Bergmann , Christoph Lameter , David Miller , Krzysztof Halasa , Peter Zijlstra , Rodolfo Giometti , Thomas Gleixner List-Id: linux-api@vger.kernel.org On Wed, Jan 12, 2011 at 5:55 AM, john stultz wrote: > So the kernel handles leap second insertion via a timer. Thus at the end > of 23:59:59, it will inject a leapsecond by setting the time back by one > second (back to 23:59:59) and setting the TIME_OOP flag. > > This timer is an absolute timer, so if someone moves the clock forward > across the 23:59:59 boundary, the adjustment will still be made. > > The patch is not broken, nor useless. It takes into account only one upcoming leap second, but ignores all the others. That's not sufficient for arbitrary adjustments.