linux-kernel - Re: Linux 5.13-rc1

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: <CAHk-=wjsQz-RJzXPu6eeZE+R9m2SH6JoreV6e_mwguitZ5_=zw@mail.gmail.com>
Date:   Mon, 10 May 2021 12:01:00 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Guenter Roeck <linux@...ck-us.net>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 5.13-rc1

On Sun, May 9, 2021 at 7:54 PM Guenter Roeck <linux@...ck-us.net> wrote:
>
> Qemu test results:
>         total: 462 pass: 460 fail: 2
> Failed tests:
>         arm:raspi2:multi_v7_defconfig:net,usb:bcm2836-rpi-2-b:initrd
>         arm:raspi2:multi_v7_defconfig:sd:net,usb:bcm2836-rpi-2-b:rootfs
>
> The raspi2 problem (a crash in of_clk_add_hw_provider) is well known.
> It was introduced with commit 6579c8d97ad7 ("clk: Mark fwnodes when
> their clock provider is added"). Unfortunately it appears that there
> is still no agreement on how to fix it.

Hmm. I see

    https://lore.kernel.org/linux-acpi/20210426065618.588144-1-tudor.ambarus@microchip.com/

and don't see any objections to that version.

Does that fix it for you too?

I'm assuming I'll get that through the usual channels.

> There is also a repeated warning
>
> WARNING: CPU: 0 PID: 1 at kernel/irq/irqdomain.c:550 irq_domain_associate+0x194/0x1f0
>
> in some pxa boot tests. It looks like that problem has been fixed in -next.

Ok, I won't worry about it then.

Thanks,

                 Linus