From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>
Subject: Re: Linux 5.12-rc7
Date: Sun, 11 Apr 2021 22:14:45 -0700 [thread overview]
Message-ID: <20210412051445.GA47322@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wiHGchP=V=a4DbDN+imjGEc=2nvuLQVoeNXNxjpU1T8pg@mail.gmail.com>
On Sun, Apr 11, 2021 at 03:41:18PM -0700, Linus Torvalds wrote:
> Oh well. rc5 was big. rc6 was small. And now rc7 is big again. In
> fact, it's the biggest rc7 (at least in number of commits) we've had
> in the 5.x series.
>
> It's mostly due to networking fixes (of which rc6 had none), and none
> of them should be all that scary, but it's never great when we have
> such a big rc. It's particularly annoying at the end of the release
> window like this.
>
> End result: I'm still waffling about the final 5.12 release. The fact
> that we have a big rc7 does make me think that I'll probably do an rc8
> this time around. But it ends up depending a bit on how the upcoming
> week goes, and if things are deathly quiet, I may end up deciding that
> an rc8 doesn't really make sense.
>
> So we'll see.
>
> Anyway, networking (both core and drivers) is over half of the rc7
> patch, with the rest being a fairly random collection of fixes all
> over. We've got other driver updates (sound, rdma, scsi, usb..) some
> fs fixes (io_uring, umount, btrfs, cifs, ocfs), minor arch fixes (arc,
> arm, parisc, powerpc, s390, x86), and other misc fixes.
>
> The shortlog is appended, although it's obviously not as nice and
> small and readable as I'd have liked at this point in the release..
>
> Please do test,
>
Build results:
total: 151 pass: 151 fail: 0
Qemu test results:
total: 460 pass: 459 fail: 1
Failed tests:
sh:rts7751r2dplus_defconfig:ata:net,virtio-net:rootfs
The failure bisects to commit 0f6925b3e8da ("virtio_net: Do not pull payload in
skb->head"). It is a spurious problem - the test passes roughly every other
time. When the failure is seen, udhcpc fails to get an IP address and aborts
with SIGTERM. So far I have only seen this with the "sh" architecture.
Guenter
next prev parent reply other threads:[~2021-04-12 5:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-11 22:41 Linux 5.12-rc7 Linus Torvalds
2021-04-12 5:14 ` Guenter Roeck [this message]
2021-04-12 16:28 ` Linus Torvalds
2021-04-12 16:31 ` Michael S. Tsirkin
2021-04-12 16:31 ` Eric Dumazet
2021-04-12 16:47 ` Eric Dumazet
2021-04-13 12:57 ` Michael S. Tsirkin
2021-04-13 13:27 ` Eric Dumazet
2021-04-13 13:33 ` Eric Dumazet
2021-04-13 13:37 ` Michael S. Tsirkin
2021-04-13 13:42 ` Eric Dumazet
2021-04-13 13:46 ` Michael S. Tsirkin
2021-04-13 13:58 ` Michael S. Tsirkin
2021-04-12 17:31 ` Guenter Roeck
2021-04-12 17:38 ` Eric Dumazet
2021-04-12 20:05 ` Guenter Roeck
2021-04-13 9:24 ` Eric Dumazet
2021-04-13 10:43 ` Eric Dumazet
2021-04-13 12:45 ` Eric Dumazet
2021-04-13 12:52 ` Michael S. Tsirkin
2021-04-12 2:03 Ronald Warsow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210412051445.GA47322@roeck-us.net \
--to=linux@roeck-us.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).