linux-kernel - Re: [PATCH 5.10 000/187] 5.10.202-rc3 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]

Message-ID: <6e45696d-fe6b-4570-8ca7-481de78a983f@nvidia.com>
Date:   Mon, 27 Nov 2023 23:37:17 +0000
From:   Jon Hunter <jonathanh@...dia.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     patches@...ts.linux.dev, linux-kernel@...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, srw@...dewatkins.net, rwarsow@....de,
        conor@...nel.org, allen.lkml@...il.com,
        linux-tegra@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH 5.10 000/187] 5.10.202-rc3 review


On 27/11/2023 23:27, Jon Hunter wrote:
> On Sun, 26 Nov 2023 15:46:55 +0000, Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 5.10.202 release.
>> There are 187 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 Tue, 28 Nov 2023 15:43:06 +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.10.202-rc3.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.10.y
>> and the diffstat can be found below.
>>
>> thanks,
>>
>> greg k-h
> 
> Failures detected for Tegra ...
> 
> Test results for stable-v5.10:
>      10 builds:	10 pass, 0 fail
>      26 boots:	26 pass, 0 fail
>      68 tests:	67 pass, 1 fail
> 
> Linux version:	5.10.202-rc3-g80dc4301c91e
> 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
> 
> Test failures:	tegra194-p2972-0000: boot.py


After commit the commit "gpio: Don't fiddle with irqchips marked as 
immutable" added, we observe the following warnings and is causing a 
test to fail ...

  WARNING KERN gpio gpiochip0: (max77620-gpio): not an immutable chip, 
please consider fixing it!
  WARNING KERN gpio gpiochip1: (tegra194-gpio): not an immutable chip, 
please consider fixing it!
  WARNING KERN gpio gpiochip2: (tegra194-gpio-aon): not an immutable 
chip, please consider fixing it!

The following upstream changes fix these ...

7d1aa08aff06 gpio: tegra: Convert to immutable irq chip
bba00555ede7 gpio: tegra186: Make the irqchip immutable
7f42aa7b008c gpio: max77620: Make the irqchip immutable

There are quite a few other drivers that were updated in a similar way, 
so the above only fix the ones we observe on Tegra.

Jon

-- 
nvpublic