linux-kernel - Re: [PATCH] hrtimer, add expiry time overflow check in hrtimer

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

Message-ID: <51632AD3.5030906@linaro.org>
Date:	Mon, 08 Apr 2013 13:38:43 -0700
From:	John Stultz <john.stultz@...aro.org>
To:	Prarit Bhargava <prarit@...hat.com>
CC:	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	stable <stable@...r.kernel.org>
Subject: Re: [PATCH] hrtimer, add expiry time overflow check in hrtimer_interrupt

On 04/08/2013 01:34 PM, Prarit Bhargava wrote:
>
> On 04/08/2013 04:19 PM, John Stultz wrote:
>> On 04/08/2013 05:47 AM, Prarit Bhargava wrote:
>>> A simple check for an overflow can resolve this problem.  Using KTIME_MAX
>>> instead of the overflow value will result in the hrtimer function being run,
>>> and the reprogramming of the timer after that.
>>>
>>> Signed-off-by: Prarit Bhargava <prarit@...hat.com>
>>> Cc: Thomas Gleixner <tglx@...utronix.de>
>>> Cc: John Stultz <john.stultz@...aro.org>
>> Prarit: Should this be tagged for -stable?
> John,
>
> Yes, this should go to -stable.  cc'd.
Also, added the cc to the commit.

thanks
-john

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