Re: Linux 5.15-rc3

From: Michael S. Tsirkin
Date: Mon Sep 27 2021 - 18:31:41 EST


On Mon, Sep 27, 2021 at 11:55:52AM -0700, Linus Torvalds wrote:
> On Mon, Sep 27, 2021 at 4:05 AM Guenter Roeck <linux@xxxxxxxxxxxx> wrote:
> >
> > On Sun, Sep 26, 2021 at 02:21:52PM -0700, Linus Torvalds wrote:
> > > So after a somewhat rocky merge window and second rc, things are now
> > > actually looking pretty normal for rc3. Knock wood.
> > >
> > > There are fixes all over, and the statistics look fairly regular, with
> > > drivers dominating as they should (since they are most of the tree).
> > > And outside of drivers, we have a fairly usual mix of changes -
> > > architecture fixes, networking, filesystems, and tooling (the latter
> > > being mostly kvm selftests).
> > >
> > > Shortlog appended, it's not too long and easy to scan through to get a
> > > flavor for the details if you happen to care.
> > >
> > > Please do give it a whirl,
> > >
> >
> > Build results:
> > total: 153 pass: 152 fail: 1
> > Failed builds:
> > mips:allmodconfig
>
> Gaah. I assume this is the
>
> arch/mips/include/asm/sibyte/bcm1480_scd.h:261: error:
> "M_SPC_CFG_CLEAR" redefined
>
> thing still.
>
> It's been pending too long in the mips tree, I'll just take the patch
> directly and finally empty your queue of build failures.
>
> > Qemu test results:
> > total: 480 pass: 479 fail: 1
> > Failed tests:
> > sparc64:sun4u:nodebug:smp:virtio-pci:net,i82559er:hd
>
> And going back to your -rc1 email, I see
>
> "The qemu runtime failure bisects to commit 694a1116b405 ("virtio: Bind
> virtio device to device-tree node"), and reverting that commit fixes the
> problem. With that patch applied, the virtio block device does not
> instantiate on sparc64. This results in a crash since that is where the
> test is trying to boot from"
>
> That commit 694a1116b405 doesn't revert cleanly, but the conflict is
> trivial (we've removed a "return 0" since then).
>
> I've added the guilty parties to the participants list, but if this
> test failure remains in rc4 I'll just do that revert at that point.

Just sent a pull with a fix for that.

> > Almost there ...
>
> Almost.
>
> Linus