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]

Date:   Mon, 10 May 2021 15:20:41 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Tudor Ambarus <tudor.ambarus@...rochip.com>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Guenter Roeck <linux@...ck-us.net>,
        Saravana Kannan <saravanak@...gle.com>,
        Stephen Boyd <sboyd@...nel.org>
Subject: Re: Linux 5.13-rc1

Just adding Greg & co explicitly to the participants to make sure
they're aware of this..

Greg? This came through your driver core tree.

                Linus

On Mon, May 10, 2021 at 12:39 PM Guenter Roeck <linux@...ck-us.net> wrote:
>
> On Mon, May 10, 2021 at 12:01:00PM -0700, Linus Torvalds wrote:
> > 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?
> >
>
> Yes, it does. It was submitted ~2 weeks ago, so I have no idea what its
> status might be (it is not in the most recent -next). I just sent a
> Tested-by:, figuring that it can't hurt.
>
> Guenter