From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from www.linutronix.de ([62.245.132.108]:57988 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751113AbbIAU0L (ORCPT ); Tue, 1 Sep 2015 16:26:11 -0400 Date: Tue, 1 Sep 2015 22:25:35 +0200 (CEST) From: Thomas Gleixner To: =?ISO-8859-15?Q?Nuno_Gon=E7alves?= cc: LKML , John Stultz , mlichvar@redhat.com, dl4mea@yahoo.de, stable@vger.kernel.org Subject: Re: Regression: can't apply frequency offsets above 1000ppm. In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323329-1935268091-1441139136=:15006" Sender: stable-owner@vger.kernel.org List-ID: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-1935268091-1441139136=:15006 Content-Type: TEXT/PLAIN; charset=UTF-8 Content-Transfer-Encoding: 8BIT On Tue, 1 Sep 2015, Nuno Gonçalves wrote: > There is a regression on the clock system since v3.16-rc5-111-g4396e05 > [1], > [1] http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4396e058c52e167729729cf64ea3dfa229637086 That commit has absolutely nothing to do with NTP. I fear your bisect went down the wrong road somewhere. > where the clock doesn't apply frequency offsets above about > 1000ppm [2]. This looks pretty familiar. The issue was introduced with commit 5e5aeb4367b (time: adjtimex: Validate the ADJ_FREQUENCY values). That patch was tagged for stable, so it got backported. The fix is in commit 29183a70b0b82 (ntp: Fixup adjtimex freq validation on 32-bit systems). That commit was tagged for stable as well, but with the extra '#3.19+' limitation. So in the worst case 5e5aeb4367b hit a stable tree < 3.19, but 29183a70b0b82 did not. Thanks, tglx --8323329-1935268091-1441139136=:15006--