[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <12419f82-3efa-7587-da50-4edf7eef99e1@arm.com>
Date: Fri, 14 May 2021 11:58:10 +0100
From: Lukasz Luba <lukasz.luba@....com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
daniel.lezcano@...aro.org, rui.zhang@...el.com
Subject: Re: [STABLE][PATCH 4.4] thermal/core/fair share: Lock the thermal
zone while looping over instances
On 5/14/21 11:56 AM, Greg KH wrote:
> 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@...r.kernel.org # 4.4
>> Signed-off-by: Lukasz Luba <lukasz.luba@....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?
s/4.14/4.19
Yes, I'm going to send them in next few hours after building and
testing.
Regards,
Lukasz
Powered by blists - more mailing lists