From: Luis Henriques <luis.henriques@canonical.com>
To: Thomas Renninger <trenn@suse.de>
Cc: stable <stable@vger.kernel.org>, prarit@redhat.com
Subject: Re: Request for inclusion of 7180dddf7c32c49975c7e7babf2b60ed450cb760 into 4.1 and 3.18
Date: Mon, 19 Oct 2015 12:19:06 +0100 [thread overview]
Message-ID: <20151019111906.GF3424@ares> (raw)
In-Reply-To: <3010888.pyN6FAPjAR@skinner>
On Tue, Oct 13, 2015 at 02:51:21PM +0200, Thomas Renninger wrote:
> Hi,
>
> while double checking whether this on is needed for 3.12 (which it is not),
> I realized that this easy patch, fixing a potential divide by zero bug,
> patches nicely with only line offset into 4.1 and 3.18 latest stable kernel
> branches.
>
> So you might want to consider taking this one.
>
With some context adjustment, I am also picking it for the 3.16 kernel.
(I'm actually also picking fa30dff9a81e ("cpufreq: intel_pstate: Remove
unnecessary type casting in div_s64() call").)
Cheers,
--
Lu�s
> commit 7180dddf7c32c49975c7e7babf2b60ed450cb760
> Author: Prarit Bhargava <prarit@redhat.com>
> Date: Mon Jun 15 13:43:29 2015 -0400
>
> intel_pstate: Fix overflow in busy_scaled due to long delay
>
> The kernel may delay interrupts for a long time which can result in timers
> being delayed. If this occurs the intel_pstate driver will crash with a
> divide by zero error:
>
> divide error: 0000 [#1] SMP
> ...
> --
> To unsubscribe from this list: send the line "unsubscribe stable" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-10-19 11:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 12:51 Request for inclusion of 7180dddf7c32c49975c7e7babf2b60ed450cb760 into 4.1 and 3.18 Thomas Renninger
2015-10-18 0:37 ` Greg KH
2015-10-19 11:19 ` Luis Henriques [this message]
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=20151019111906.GF3424@ares \
--to=luis.henriques@canonical.com \
--cc=prarit@redhat.com \
--cc=stable@vger.kernel.org \
--cc=trenn@suse.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).