linux-kernel - Re: [PATCH 6.1 000/132] 6.1.25-rc2 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:   Wed, 19 Apr 2023 05:46:50 -0700
From:   Ron Economos <re@...z.net>
To:     Conor.Dooley@...rochip.com, gregkh@...uxfoundation.org,
        stable@...r.kernel.org, hi@...ssa.is
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, jonathanh@...dia.com,
        f.fainelli@...il.com, sudipm.mukherjee@...il.com,
        srw@...dewatkins.net, rwarsow@....de
Subject: Re: [PATCH 6.1 000/132] 6.1.25-rc2 review

On 4/19/23 4:58 AM, Conor.Dooley@...rochip.com wrote:
> On 19/04/2023 10:40, Greg Kroah-Hartman wrote:
>
>> This is the start of the stable review cycle for the 6.1.25 release.
>> There are 132 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 Fri, 21 Apr 2023 09:36:33 +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/v6.x/stable-review/patch-6.1.25-rc2.gz
>> or in the git tree and branch at:
>>           git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y
>> and the diffstat can be found below.
>>
>> thanks,
>>
>> greg k-h
>>
>> Alyssa Ross <hi@...ssa.is>
>>       purgatory: fix disabling debug info
> Alyssa provided a custom backport of this that did not require
> picking up Heiko's patch below, but it did not seem to get
> picked up.
> Lore is ~dead for me, so all I can give you here is her message-id
> for the custom backport: <20230418155237.2ubcusqc52nufmow@...0>
>
> Heiko's patch is dead code as you've (rightly) not backported
> any of the users.
>    
>> Heiko Stuebner <heiko.stuebner@...ll.eu>
>>       RISC-V: add infrastructure to allow different str* implementations
>
>
>> Alexandre Ghiti <alexghiti@...osinc.com>
>>       riscv: Do not set initial_boot_params to the linear address of the dtb
> This one should also be dropped, either the whole series or
> none of it please!
>
> Alex has said he'll send the lot in a way that avoids confusion.
>
> Otherwise, my testing passed.
>
> Thanks,
> Conor.

The "riscv: Do not set initial_boot_params to the linear address of the 
dtb" patch is fatal. Definitely needs to be dropped.

[    0.000000] Hardware name: SiFive HiFive Unmatched A00 (DT)
[    0.000000] epc : fdt_check_header+0xe/0x230
[    0.000000]  ra : __unflatten_device_tree+0x4e/0x320
[    0.000000] epc : ffffffff80ae48e6 ra : ffffffff808bba16 sp : 
ffffffff81803e0
[    0.000000]  gp : ffffffff81a3d390 tp : ffffffff81811200 t0 : 
ffffffc6fefff00
[    0.000000]  t1 : 000000047fff0000 t2 : 65736552203a616d s0 : 
ffffffff81803e0
[    0.000000]  s1 : 0000000040000000 a0 : 0000000040000000 a1 : 
000000000000000
[    0.000000]  a2 : ffffffff81a43188 a3 : ffffffff80c3fbd0 a4 : 
000000000000000
[    0.000000]  a5 : 0000000000000000 a6 : 0000000000000000 a7 : 
000000000000000
[    0.000000]  s2 : 00000000fff63036 s3 : ffffffff81a43188 s4 : 
000000000000000
[    0.000000]  s5 : ffffffff80c3fbd0 s6 : 0000000000000000 s7 : 
000000000000000
[    0.000000]  s8 : 00000000fff63036 s9 : 00000000fffcbf60 s10: 
000000000000000
[    0.000000]  s11: 00000000fffcbf60 t3 : ffffffff80e12288 t4 : 
ffffffff80e1228
[    0.000000]  t5 : ffffffff80e12288 t6 : ffffffff80e122a0
[    0.000000] status: 0000000200000100 badaddr: 0000000040000001 cause: 
000000d
[    0.000000] [<ffffffff80ae48e6>] fdt_check_header+0xe/0x230
[    0.000000] ---[ end trace 0000000000000000 ]---
[    0.000000] Kernel panic - not syncing: Attempted to kill the idle task!
[    0.000000] ---[ end Kernel panic - not syncing: Attempted to kill 
the idle -