From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754858AbbINNqU (ORCPT ); Mon, 14 Sep 2015 09:46:20 -0400 Received: from foss.arm.com ([217.140.101.70]:46339 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752655AbbINNqS (ORCPT ); Mon, 14 Sep 2015 09:46:18 -0400 Date: Mon, 14 Sep 2015 14:46:05 +0100 From: Mark Rutland To: John Stultz , Cyril Hrubis , Wang YanQing Cc: ltp@lists.linux.it, will.deacon@arm.com, linux-kernel@vger.kernel.org Subject: LTP and commit e1d7ba8735551ed7 ("time: Always make sure wall_to_monotonic isn't positive") Message-ID: <20150914134603.GD7002@leverpostej> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, While testing v4.3-rc1 with the LTP, we spotted failures in a couple of timekeeping tests, which seem to be a result of commit e1d7ba8735551ed7 ("time: Always make sure wall_to_monotonic isn't positive"). In both cases this is because the new time would be before the boot time, so I guess these are covered by the caveat at the end of the commit message. settimeofday01 [1] tries tries to settimeofday() with a timeval 100s and 100ns, while clock_gettime02 [2] tries to clock_settime to 1s and 100ns. Neither expect -EINVAL, and report failure with the new behaviour. While I don't know that any "real" software is affected, I thought I should let you know. Thanks, Mark. [1] https://github.com/linux-test-project/ltp/blob/20150903/testcases/kernel/syscalls/settimeofday/settimeofday01.c [2] https://github.com/linux-test-project/ltp/blob/20150903/testcases/kernel/timers/clock_settime/clock_settime02.c