From: Thomas Gleixner <tglx@linutronix.de>
To: "Nuno Gonçalves" <nunojpg@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
John Stultz <john.stultz@linaro.org>,
mlichvar@redhat.com, dl4mea@yahoo.de, stable@vger.kernel.org
Subject: Re: Regression: can't apply frequency offsets above 1000ppm.
Date: Tue, 1 Sep 2015 22:25:35 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1509012207140.15006@nanos> (raw)
In-Reply-To: <CAEXMXLRPvKqGvzTiqb8mKNXOS+beaB2AJCdb=ZCwHwn1Nyk-yQ@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 899 bytes --]
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
next parent reply other threads:[~2015-09-01 20:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEXMXLRPvKqGvzTiqb8mKNXOS+beaB2AJCdb=ZCwHwn1Nyk-yQ@mail.gmail.com>
2015-09-01 20:25 ` Thomas Gleixner [this message]
2015-09-01 20:30 ` Regression: can't apply frequency offsets above 1000ppm John Stultz
2015-09-01 20:45 ` Thomas Gleixner
2015-09-02 0:36 ` Nuno Gonçalves
2015-09-02 1:03 ` John Stultz
2015-09-02 1:14 ` Nuno Gonçalves
2015-09-02 7:39 ` Miroslav Lichvar
2015-09-02 23:16 ` John Stultz
2015-09-03 10:10 ` Nuno Gonçalves
2015-09-03 11:26 ` Miroslav Lichvar
2015-09-05 0:57 ` John Stultz
2015-09-05 1:00 ` John Stultz
2015-09-05 1:39 ` defects for uses of abs(u64) (was: Re: Regression: can't apply frequency offsets above 1000ppm) Joe Perches
2015-09-23 7:21 ` Neil Brown
2015-09-05 13:41 ` Regression: can't apply frequency offsets above 1000ppm Nuno Gonçalves
2015-09-09 0:52 ` John Stultz
2015-09-09 1:00 ` Nuno Gonçalves
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=alpine.DEB.2.11.1509012207140.15006@nanos \
--to=tglx@linutronix.de \
--cc=dl4mea@yahoo.de \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlichvar@redhat.com \
--cc=nunojpg@gmail.com \
--cc=stable@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