mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Stultz <john.stultz@linaro.org>
To: lkml <linux-kernel@vger.kernel.org>
Cc: John Stultz <john.stultz@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>,
	Richard Cochran <richardcochran@gmail.com>,
	Prarit Bhargava <prarit@redhat.com>,
	Sharvil Nanavati <sharvil@google.com>,
	Paul Turner <pjt@google.com>, Andrew Hunter <ahh@google.com>,
	Aaron Jacobs <jacobsa@google.com>,
	Richard Larocque <rlarocque@google.com>
Subject: [PATCH 0/4] Time related fixes for 3.17/stable
Date: Fri, 12 Sep 2014 14:22:20 -0700	[thread overview]
Message-ID: <1410556944-14944-1-git-send-email-john.stultz@linaro.org> (raw)

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@linutronix.de>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Richard Cochran <richardcochran@gmail.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Sharvil Nanavati <sharvil@google.com>
Cc: Paul Turner <pjt@google.com>
Cc: Andrew Hunter <ahh@google.com>
Cc: Aaron Jacobs <jacobsa@google.com>
Cc: Richard Larocque <rlarocque@google.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


             reply	other threads:[~2014-09-12 21:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-12 21:22 John Stultz [this message]
2014-09-12 21:22 ` [PATCH 1/4] jiffies: Fix timeval conversion to jiffies John Stultz
2014-09-12 21:22 ` [PATCH 2/4] alarmtimer: Return relative times in timer_gettime John Stultz
2014-09-12 21:22 ` [PATCH 3/4] alarmtimer: Do not signal SIGEV_NONE timers John Stultz
2014-09-12 21:22 ` [PATCH 4/4] alarmtimer: Lock k_itimer during timer callback John Stultz

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=1410556944-14944-1-git-send-email-john.stultz@linaro.org \
    --to=john.stultz@linaro.org \
    --cc=ahh@google.com \
    --cc=jacobsa@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=pjt@google.com \
    --cc=prarit@redhat.com \
    --cc=richardcochran@gmail.com \
    --cc=rlarocque@google.com \
    --cc=sharvil@google.com \
    --cc=tglx@linutronix.de \
    /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

Powered by JetHome