From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from mail.linuxfoundation.org ([140.211.169.12]:56176 "EHLO
        mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752888AbdFROtq (ORCPT
        <rfc822;stable@vger.kernel.org>); Sun, 18 Jun 2017 10:49:46 -0400
Date: Sun, 18 Jun 2017 22:48:59 +0800
From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: dvyukov@google.com, john.stultz@linaro.org, kcc@google.com,
        peterz@infradead.org, syzkaller@googlegroups.com,
        stable@vger.kernel.org
Subject: Re: [PATCH backport 4.11] alarmtimer: Rate limit periodic intervals
Message-ID: <20170618144859.GA3817@kroah.com>
References: <1497783192143216@kroah.com>
 <alpine.DEB.2.20.1706181421060.2428@nanos>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.20.1706181421060.2428@nanos>
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

On Sun, Jun 18, 2017 at 02:24:37PM +0200, Thomas Gleixner wrote:
> commit ff86bf0c65f14346bf2440534f9ba5ac232c39a0 upstream.
> 
> The alarmtimer code has another source of potentially rearming itself too
> fast. Interval timers with a very samll interval have a similar CPU hog
> effect as the previously fixed overflow issue.

<snip>

thanks for the backport, now applied to all stable trees.

greg k-h