linux-kernel - Re: [GIT pull] ntp updates for 2.6.31

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 16 Jun 2009 11:06:47 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	john stultz <johnstul@...ibm.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Miroslav Lichvar <mlichvar@...hat.com>
Subject: Re: [GIT pull] ntp updates for 2.6.31

* john stultz <johnstul@...ibm.com> wrote:

> Linus,
>     You probably didn't see this before merging.  Could you yank the
> above two patches?  Miroslav (RH package maintainer for ntpd), has
> voiced concerns that the SHIFT_PLL patch breaks the NTP design and is
> worried it may negatively effect NTP networks of systems running with
> different SHIFT_PLL values.
> 
> While the patch does greatly improve NTP convergence times, and so 
> far no negative results have been seen in tests, its out of an 
> abundance of caution and a desire to keep the adjtimex behavior 
> stable that I requested Thomas and Ingo to hold off on merging 
> this patch, while I work with Miroslav to see if we cannot get the 
> same benefit by adjusting the userspace NTPd.

As i explained it in previous threads i disagree. The only 
technically correct direction is to improve NTP stabilization and 
convergence times as much as possible. [*]

( [*] Without getting into over-compensation and without starting to
      oscillate instead of converging - that would be a bug, but 
      such a bug has not been reported so far. )

The 'concern' voiced was that: "what if other OSs converge slower in 
a cluster and now we have a faster OS in the mix". This absolutely 
ignores the other 99% of cases where people would have crappier 
convergence after the revert and for no good reason.

And even regarding that 1% example, well, duh: different OSes have 
different convergence times, fundamentally so - such as Linux had a 
very slow convergence time from about 2.6.18 up to recent kernels 
due to a bug. Now it's converging even faster ...

So i dont think that "Linux is too good" is a good basis to 
artificially make Linux's NTP code crappier. Really. We dont 'play 
nice' by being equally crappy.

Each OS should converge back to the correct time _as fast as 
physically possible_. If this is a problem and if someone wants 
crappy time and longer periods of convergence for some odd reason 
then that header file change can be edited by hand even. It's not 
like it's that hard to change, if there's genuine interest.

So i'm against any revert on this basis. If another basis comes up 
we can reconsider of course. What do you think?

	Ingo

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/