linux-kernel - Re: [PATCH 5.17 00/39] 5.17.1-rc1 review

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 26 Mar 2022 10:55:47 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Naresh Kamboju <naresh.kamboju@...aro.org>
Cc:     Rob Clark <robdclark@...omium.org>, linux-kernel@...r.kernel.org,
        stable@...r.kernel.org, torvalds@...ux-foundation.org,
        akpm@...ux-foundation.org, linux@...ck-us.net, shuah@...nel.org,
        patches@...nelci.org, lkft-triage@...ts.linaro.org, pavel@...x.de,
        jonathanh@...dia.com, f.fainelli@...il.com,
        sudipm.mukherjee@...il.com, slade@...dewatkins.com
Subject: Re: [PATCH 5.17 00/39] 5.17.1-rc1 review

On Sat, Mar 26, 2022 at 10:24:39AM +0530, Naresh Kamboju wrote:
> On Fri, 25 Mar 2022 at 20:50, Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 5.17.1 release.
> > There are 39 patches in this series, all will be posted as a response
> > to this one.  If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Sun, 27 Mar 2022 15:04:08 +0000.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> >         https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.17.1-rc1.gz
> > or in the git tree and branch at:
> >         git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.17.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
> 
> arm64 qcom db410c device crashed [1]
> 
> [   10.823905] Internal error: Oops: 96000004 [#1] PREEMPT SMP
> [   10.876029] CPU: 1 PID: 193 Comm: kworker/1:2 Not tainted 5.17.1-rc1 #1
> [   10.876047] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT)
> [   10.876054] Workqueue: pm pm_runtime_work
> [   10.876076] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> [   10.876087] pc : hrtimer_active+0x14/0x80
> [   10.876102] lr : hrtimer_cancel+0x28/0x70
> 
> 
> The following patch fixes the problem.
> 
> >From 05afd57f4d34602a652fdaf58e0a2756b3c20fd4 Mon Sep 17 00:00:00 2001
> From: Rob Clark <robdclark@...omium.org>
> Date: Tue, 8 Mar 2022 10:48:44 -0800
> Subject: drm/msm/gpu: Fix crash on devices without devfreq support (v2)
> 
> Avoid going down devfreq paths on devices where devfreq is not
> initialized.
> 
> v2: Change has_devfreq() logic [Dmitry]
> 
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
> Reported-by: Anders Roxell <anders.roxell@...aro.org>
> Signed-off-by: Rob Clark <robdclark@...omium.org>
> Fixes: 6aa89ae1fb04 ("drm/msm/gpu: Cancel idle/boost work on suspend")
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
> Link: https://lore.kernel.org/r/20220308184844.1121029-1-robdclark@gmail.com
> ---
>  drivers/gpu/drm/msm/msm_gpu_devfreq.c | 30 +++++++++++++++++++++++++-----
>  1 file changed, 25 insertions(+), 5 deletions(-)
> 
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
> 

Now queued up, but note, this problem was already present in 5.17.0,
right?

thanks,

greg k-h