linux-kernel - [PATCH 0/4] Time related fixes for 3.17/stable

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-next>] [day] [month] [year] [list]

Message-Id: <1410556944-14944-1-git-send-email-john.stultz@linaro.org>
Date:	Fri, 12 Sep 2014 14:22:20 -0700
From:	John Stultz <john.stultz@...aro.org>
To:	lkml <linux-kernel@...r.kernel.org>
Cc:	John Stultz <john.stultz@...aro.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...nel.org>,
	Richard Cochran <richardcochran@...il.com>,
	Prarit Bhargava <prarit@...hat.com>,
	Sharvil Nanavati <sharvil@...gle.com>,
	Paul Turner <pjt@...gle.com>, Andrew Hunter <ahh@...gle.com>,
	Aaron Jacobs <jacobsa@...gle.com>,
	Richard Larocque <rlarocque@...gle.com>
Subject: [PATCH 0/4] Time related fixes for 3.17/stable

Hey Thomas, Ingo,

  Here are a few fixes for 3.17/stable that came in over the last week or so.

The first is a fix to the timeval to jiffies conversion that was incorrectly
rounding up by one even when the value divided precisely. This issue is
apparently quite long standing, but shows up as in increasing timeout when
folks re-use the returned old_value from setitimer.

The second group are yet further fixes to the alarmtimer code. This time
catching incorrect timer_gettime semantics as well as fixes for improper
signaling and locking. These all go back to 3.0, and the timer_gettime
change could cause problems with existing apps, but I suspect that aspect
of the interface hasn't been used much until recently.

These are against tip/timers/urgent, and have run successfully through
my timekeeping tests for x86_64, i386 and arm.

Let me know if you have any comments or objections.

thanks
-john

Cc: Thomas Gleixner <tglx@...utronix.de>
Cc: Ingo Molnar <mingo@...nel.org>
Cc: Richard Cochran <richardcochran@...il.com>
Cc: Prarit Bhargava <prarit@...hat.com>
Cc: Sharvil Nanavati <sharvil@...gle.com>
Cc: Paul Turner <pjt@...gle.com>
Cc: Andrew Hunter <ahh@...gle.com>
Cc: Aaron Jacobs <jacobsa@...gle.com>
Cc: Richard Larocque <rlarocque@...gle.com>

Pull request below if you'd prefer to take it that way:


The following changes since commit 9bf2419fa7bffa16ce58a4d5c20399eff8c970c9:
  timekeeping: Update timekeeper before updating vsyscall and pvclock (2014-09-06 12:58:18 +0200)

are available in the git repository at:

  https://git.linaro.org/people/john.stultz/linux.git fortglx/3.17/time

for you to fetch changes up to 474e941bed9262f5fa2394f9a4a67e24499e5926:

  alarmtimer: Lock k_itimer during timer callback (2014-09-12 13:59:12 -0700)

----------------------------------------------------------------
Andrew Hunter (1):
      jiffies: Fix timeval conversion to jiffies

Richard Larocque (3):
      alarmtimer: Return relative times in timer_gettime
      alarmtimer: Do not signal SIGEV_NONE timers
      alarmtimer: Lock k_itimer during timer callback

 include/linux/jiffies.h  | 12 ------------
 kernel/time/alarmtimer.c | 34 +++++++++++++++++++++++-----------
 kernel/time/time.c       | 56 +++++++++++++++++++++++++++++++-------------------------
 3 files changed, 54 insertions(+), 48 deletions(-)

Andrew Hunter (1):
  jiffies: Fix timeval conversion to jiffies

Richard Larocque (3):
  alarmtimer: Return relative times in timer_gettime
  alarmtimer: Do not signal SIGEV_NONE timers
  alarmtimer: Lock k_itimer during timer callback

 include/linux/jiffies.h  | 12 -----------
 kernel/time/alarmtimer.c | 34 +++++++++++++++++++----------
 kernel/time/time.c       | 56 +++++++++++++++++++++++++++---------------------
 3 files changed, 54 insertions(+), 48 deletions(-)

-- 
1.9.1

--
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/