linux-kernel - Re: [PATCH] alarmtimer: don't rate limit one-shot timers

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]

Date:   Mon, 24 Jul 2017 11:21:22 -0700
From:   Greg KH <greg@...ah.com>
To:     Greg Hackmann <ghackmann@...gle.com>
Cc:     John Stultz <john.stultz@...aro.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ben Fennema <fennema@...gle.com>, linux-kernel@...r.kernel.org,
        stable@...r.kernel.org
Subject: Re: [PATCH] alarmtimer: don't rate limit one-shot timers

On Mon, Jul 24, 2017 at 10:19:24AM -0700, Greg Hackmann wrote:
> Commit ff86bf0c65f1 ("alarmtimer: Rate limit periodic intervals") sets a
> minimum bound on the alarm timer interval.  This minimum bound shouldn't
> be applied if the interval is 0.  Otherwise, one-shot timers will be
> converted into periodic ones.
> 
> This patch is against 4.9.39, and is only needed in -stable trees.
> 4.13-rc2 isn't impacted due to a later refactoring.

What refactoring patch fixed this up?

> Fixes: ff86bf0c65f1 ("alarmtimer: Rate limit periodic intervals")

As this was a 4.12 patch, 4.12-stable needs this fix as well, right?

Also, was there some test-case that you caught this with that perhaps
could be added to LTP or kselftests?

thanks,

greg k-h