linux-kernel - [PATCH 0/4] Time fixes for 3.6

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: <1345595449-34965-1-git-send-email-john.stultz@linaro.org>
Date:	Tue, 21 Aug 2012 20:30:45 -0400
From:	John Stultz <john.stultz@...aro.org>
To:	linux-kernel <linux-kernel@...r.kernel.org>
Cc:	John Stultz <john.stultz@...aro.org>,
	Ingo Molnar <mingo@...nel.org>,
	Prarit Bhargava <prarit@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andreas Schwab <schwab@...ux-m68k.org>
Subject: [PATCH 0/4] Time fixes for 3.6

Thomas, Ingo,
	Here are four small time fixes for 3.6
that apply against tip/timers/urgent.

One patch resolves the suspend issue Andreas saw.

The next two are casting fixes for potential overflows
on 32bits, that Andreas found, but haven't been observed
in the wild.

Finally the last one fixes an issue I found in my own
testing w/ the _COARSE clocksources.

Please take a look at them and let me know if you have
any thoughts or objections.

Cc: Ingo Molnar <mingo@...nel.org>
Cc: Prarit Bhargava <prarit@...hat.com>
Cc: Thomas Gleixner <tglx@...utronix.de>
Cc: Andreas Schwab <schwab@...ux-m68k.org>

Andreas Schwab (1):
  time: Fix casting issue in timekeeping_forward_now

John Stultz (3):
  time: Ensure we normalize the timekeeper in tk_xtime_add
  time: Avoid potential shift-overflow with large shift values
  time: Avoid making adjustments if we havne't accumulated anything

 kernel/time/timekeeping.c |   11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

-- 
1.7.9.5

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