Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965769AbbLPKO5 (ORCPT ); Wed, 16 Dec 2015 05:14:57 -0500 Received: from mx1.redhat.com ([209.132.183.28]:51198 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932751AbbLPKOz (ORCPT ); Wed, 16 Dec 2015 05:14:55 -0500 Date: Wed, 16 Dec 2015 11:14:49 +0100 From: Miroslav Lichvar To: John Stultz Cc: lkml , Thomas Gleixner , Richard Cochran , Prarit Bhargava , Andy Lutomirski Subject: Re: [RFC][PATCH v3] timekeeping: Cap adjustments so they don't exceed the maxadj value Message-ID: <20151216101449.GA6207@localhost> References: <1450244886-9931-1-git-send-email-john.stultz@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1450244886-9931-1-git-send-email-john.stultz@linaro.org> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 867 Lines: 24 On Tue, Dec 15, 2015 at 09:48:06PM -0800, John Stultz wrote: > Thus its been occasionally noted that users have seen > confusing warnings like: > > Adjusting tsc more than 11% (5941981 vs 7759439) > v2: Catch single unit adjustment that was being made > repeatedly to push us past the limit, as pointed > out by Miroslav. > v3: Fix off-by-one case that could result in warning > still triggering, pointed out by Miroslav. Looks good to me. There are no warnings in the simulator and chronyd still seems to be working as expected. Tested-by: Miroslav Lichvar -- Miroslav Lichvar -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/