linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Lukasz Luba <lukasz.luba@arm.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	daniel.lezcano@linaro.org, rui.zhang@intel.com
Subject: Re: [STABLE][PATCH 4.4] thermal/core/fair share: Lock the thermal zone while looping over instances
Date: Fri, 14 May 2021 12:56:13 +0200	[thread overview]
Message-ID: <YJ5XTW9TYvv7wYr6@kroah.com> (raw)
In-Reply-To: <20210514104916.19975-1-lukasz.luba@arm.com>

On Fri, May 14, 2021 at 11:49:16AM +0100, Lukasz Luba wrote:
> commit fef05776eb02238dcad8d5514e666a42572c3f32 upstream.
> 
> The tz->lock must be hold during the looping over the instances in that
> thermal zone. This lock was missing in the governor code since the
> beginning, so it's hard to point into a particular commit.
> 
> CC: stable@vger.kernel.org # 4.4
> Signed-off-by: Lukasz Luba <lukasz.luba@arm.com>
> ---
> Hi all,
> 
> I've backported my patch which was sent to LKML:
> https://lore.kernel.org/linux-pm/20210422153624.6074-2-lukasz.luba@arm.com/
> 
> The upstream patch failed while applying:
> https://lore.kernel.org/stable/16206371483193@kroah.com/
> 
> This patch should apply to stable v4.4.y, on top of stable tree branch:
> linux-4.4.y which head was at:
> commit 47127fcd287c ("Linux 4.4.268")

What about 4.9, 4.14, 4.14, and 5.4 releases?  They need this fix as
well, right?

thanks,

greg k-h

  reply	other threads:[~2021-05-14 10:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14 10:49 [STABLE][PATCH 4.4] thermal/core/fair share: Lock the thermal zone while looping over instances Lukasz Luba
2021-05-14 10:56 ` Greg KH [this message]
2021-05-14 10:58   ` Lukasz Luba
2021-05-17 10:29     ` Greg KH

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=YJ5XTW9TYvv7wYr6@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=rui.zhang@intel.com \
    --cc=stable@vger.kernel.org \
    /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).