From: Greg KH <greg@kroah.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Greg Hackmann <ghackmann@google.com>,
John Stultz <john.stultz@linaro.org>,
Ben Fennema <fennema@google.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] alarmtimer: don't rate limit one-shot timers
Date: Tue, 25 Jul 2017 11:01:48 -0700 [thread overview]
Message-ID: <20170725180148.GA24730@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1707250859530.1856@nanos>
On Tue, Jul 25, 2017 at 09:00:42AM +0200, Thomas Gleixner wrote:
> On Mon, 24 Jul 2017, Greg KH wrote:
>
> > On Mon, Jul 24, 2017 at 02:41:10PM -0700, Greg Hackmann wrote:
> > > On 07/24/2017 11:21 AM, Greg KH wrote:
> > > > 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?
> > >
> > > f2c45807d399 ("alarmtimer: Switch over to generic set/get/rearm routine")
> >
> > Ick, yeah, that's not a stable patch :)
> >
> > > > As this was a 4.12 patch, 4.12-stable needs this fix as well, right?
> > >
> > > Looks like it, but I haven't actually tried 4.12 yet to confirm.
> > >
> > > > Also, was there some test-case that you caught this with that perhaps
> > > > could be added to LTP or kselftests?
> > >
> > > Unfortunately not a direct testcase. This first showed up as a regression
> > > in AOSP's userspace Bluetooth stack, which uses CLOCK_BOOTTIME_ALARM
> > > internally.
> > >
> > > I'm working on a patch to add one-shot timer testcases to set-timer-lat.c,
> > > which would have caught this. (I wrote a very rough test program to make
> > > sure this patch fixes the regression, but set-timer-lat.c already exists and
> > > is more comprehensive.)
> >
> > Ok, thanks for the information.
> >
> > John and Thomas, any objection for me to take the original patch here in
> > the stable trees to fix this issue?
>
> No. I borked that when I was 'fixing' that DoS issue :(
>
> Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Thanks for the review.
Greg, can you provide a version of this for 4.12-stable? It doesn't
apply there as-is.
thanks,
greg k-h
next prev parent reply other threads:[~2017-07-25 18:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 17:19 [PATCH] alarmtimer: don't rate limit one-shot timers Greg Hackmann
2017-07-24 18:21 ` Greg KH
2017-07-24 21:41 ` Greg Hackmann
2017-07-24 21:55 ` Greg KH
2017-07-25 7:00 ` Thomas Gleixner
2017-07-25 18:01 ` Greg KH [this message]
2017-07-25 19:42 ` Greg Hackmann
2017-07-25 21:43 ` Patch "alarmtimer: don't rate limit one-shot timers" has been added to the 4.12-stable tree gregkh
2017-07-25 21:43 ` [PATCH] alarmtimer: don't rate limit one-shot timers Greg KH
2017-07-25 18:05 ` Patch "alarmtimer: don't rate limit one-shot timers" has been added to the 3.18-stable tree gregkh
2017-07-25 18:05 ` Patch "alarmtimer: don't rate limit one-shot timers" has been added to the 4.4-stable tree gregkh
2017-07-25 18:05 ` Patch "alarmtimer: don't rate limit one-shot timers" has been added to the 4.9-stable tree gregkh
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=20170725180148.GA24730@kroah.com \
--to=greg@kroah.com \
--cc=fennema@google.com \
--cc=ghackmann@google.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).