linux-kernel - Re: [PATCH 5.15 000/136] 5.15.64-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 for Android: free password hash cracker in your pocket

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

Message-ID: <e9834880-c16e-e269-30ba-3fa8a94ba1af@nvidia.com>
Date:   Tue, 30 Aug 2022 11:32:24 +0100
From:   Jon Hunter <jonathanh@...dia.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org
Cc:     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,
        f.fainelli@...il.com, sudipm.mukherjee@...il.com,
        slade@...dewatkins.com,
        "linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>
Subject: Re: [PATCH 5.15 000/136] 5.15.64-rc1 review

Hi Greg,

On 29/08/2022 11:57, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.15.64 release.
> There are 136 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 Wed, 31 Aug 2022 10:57:37 +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.15.64-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.15.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h


I have been out on vacation and unfortunately some boot issues were 
introduced for Tegra back in 5.15.61 ...

Test results for stable-v5.15:
     10 builds:	10 pass, 0 fail
     32 boots:	28 pass, 4 fail
     68 tests:	68 pass, 0 fail

Linux version:	5.15.64-rc1-g881ab4a7404d
Boards tested:	tegra124-jetson-tk1, tegra186-p2771-0000,
                 tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000,
                 tegra20-ventana, tegra210-p2371-2180,
                 tegra210-p3450-0000, tegra30-cardhu-a04

Boot failures:	tegra186-p2771-0000, tegra194-p2972-0000,
                 tegra194-p3509-0000+p3668-0000


Fortunately, these boot issues are specific to Tegra and were caused by 
commit a7f751d4e830c5a2ac9e9908df43e8d29b7d3b22 ("arm64: tegra: Mark 
BPMP channels as no-memory-wc"). This commit had the fixes tag populated 
but it has a dependency on mainline commit a4740b148a04 ("firmware: 
tegra: bpmp: Do only aligned access to IPC memory area") which did not 
have any fixes tag populated.

Can you pull mainline commit a4740b148a04 ("firmware: tegra: bpmp: Do 
only aligned access to IPC memory area") into 5.15.y, 5.18.y and 5.19.y? 
Fine if you want to do it for the next stable update.

Sorry about this. In future I will definitely make sure that someone is 
monitoring this while I am away.

Thanks
Jon

-- 
nvpublic