From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com ([66.111.4.25]:36591 "EHLO out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754377AbdGXSV3 (ORCPT ); Mon, 24 Jul 2017 14:21:29 -0400 Date: Mon, 24 Jul 2017 11:21:22 -0700 From: Greg KH To: Greg Hackmann Cc: John Stultz , Thomas Gleixner , Ben Fennema , linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH] alarmtimer: don't rate limit one-shot timers Message-ID: <20170724182122.GA6539@kroah.com> References: <20170724171924.27898-1-ghackmann@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170724171924.27898-1-ghackmann@google.com> Sender: stable-owner@vger.kernel.org List-ID: 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