From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.16-rc1
Date: Sun, 14 Nov 2021 20:56:16 -0800 [thread overview]
Message-ID: <20211115045616.GA1012538@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wjF=JzLkCi2wV+G=f8OWa5rNjPsZd2RMFG5MHwKZPgYvw@mail.gmail.com>
On Sun, Nov 14, 2021 at 02:28:55PM -0800, Linus Torvalds wrote:
> It's been two weeks, and the merge window is thus closed.
>
> I actually anticipated more problems during the merge window than we
> hit - I was traveling with a laptop for a few days early on in the
> merge window, and that's usually fairly painful. But - knock wood - it
> all worked out fine. Partly thanks to a lot of people sending in their
> pull requests fairly early, so that I could get a bit of a head start
> before travels. But partly also because I didn't end up having any
> "uhhuh, things aren't working and now I need to bisect where they
> broke" events for me on any of my machines. At least yet.
>
> So who knows? Maybe this will be one of those painless releases where
> everything just works.
>
I don't think so.
Build results:
total: 153 pass: 141 fail: 12
Failed builds:
arm:allmodconfig
arm64:allmodconfig
csky:defconfig
csky:allmodconfig
mips:allmodconfig
parisc:allmodconfig
powerpc:allmodconfig
powerpc:ppc6xx_defconfig
riscv32:allmodconfig
riscv:allmodconfig
s390:allmodconfig
sparc64:allmodconfig
Qemu test results:
total: 482 pass: 436 fail: 46
Failed tests:
<all mips>
ppc64:mac99:ppc64_book3s_defconfig:smp:net,ne2k_pci:initrd
ppc64:mac99:ppc64_book3s_defconfig:smp:net,pcnet:ide:rootfs
ppc64:mac99:ppc64_book3s_defconfig:smp:net,e1000:sdhci:mmc:rootfs
ppc64:mac99:ppc64_book3s_defconfig:smp:net,e1000e:nvme:rootfs
ppc64:mac99:ppc64_book3s_defconfig:smp:net,virtio-net:scsi[DC395]:rootfs
<all sheb>
<all sparc32>
<all xtensa>
Various compile errors:
arm:allmodconfig
arm64:allmodconfig
riscv32:allmodconfig
riscv64:allmodconfig
s390:allmodconfig
In function 'memcmp',
inlined from 'kasan_memcmp' at lib/test_kasan.c:897:2:
include/linux/fortify-string.h:263:25: error:
call to '__read_overflow' declared with attribute error: detected read beyond size of object
csky:defconfig
sparc64:allmodconfig
fs/netfs/read_helper.c: In function 'netfs_rreq_unlock':
fs/netfs/read_helper.c:435:25: error: implicit declaration of function 'flush_dcache_folio'
mips:allmodconfig
ERROR: modpost: missing MODULE_LICENSE() in drivers/pci/controller/pcie-mt7621.o
ERROR: modpost: "mips_cm_unlock_other" [drivers/pci/controller/pcie-mt7621.ko] undefined!
ERROR: modpost: "mips_cpc_base" [drivers/pci/controller/pcie-mt7621.ko] undefined!
ERROR: modpost: "mips_cm_lock_other" [drivers/pci/controller/pcie-mt7621.ko] undefined!
ERROR: modpost: "mips_cm_is64" [drivers/pci/controller/pcie-mt7621.ko] undefined!
ERROR: modpost: "mips_gcr_base" [drivers/pci/controller/pcie-mt7621.ko] undefined!
parisc:allmodconfig
arch/parisc/include/asm/jump_label.h: In function 'arch_static_branch':
arch/parisc/include/asm/jump_label.h:18:18: error: expected ':' before '__stringify'
and other similar errors.
drivers/gpu/drm/msm/msm_drv.h:531: error: "COND" redefined
arch/parisc/include/asm/assembly.h:37: note: this is the location of the previous definition
powerpc:allmodconfig
fs/ntfs/aops.c: In function 'ntfs_write_mst_block':
fs/ntfs/aops.c:1311:1: error: the frame size of 2240 bytes is larger than 2048 bytes
powerpc:ppc6xx_defconfig
arch/powerpc/platforms/83xx/mcu_mpc8349emitx.c: In function 'mcu_remove':
arch/powerpc/platforms/83xx/mcu_mpc8349emitx.c:189:13: error: unused variable 'ret'
With gcc 5.4, mips:mapta_defconfig
mips-linux-gcc.br_real: error: unrecognized command line option ‘-Wimplicit-fallthrough=5’
Various powerpc qemu builds:
arch/powerpc/mm/slice.c: In function ‘slice_get_unmapped_area’:
arch/powerpc/mm/slice.c:639:1: error: the frame size of 1056 bytes is larger than 1024 bytes
sheb, gcc-6.3.0:
sh4eb-linux-gcc.br_real: error: unrecognized command line option ‘-Wimplicit-fallthrough=5’
sparc32, gcc 6.5.0:
sparc64-linux-gcc.br_real: error: unrecognized command line option ‘-Wimplicit-fallthrough=5’
xtensa, gcc 6.3.0 and gcc 6.4.0:
xtensa-linux-gcc.br_real: error: unrecognized command line option ‘-Wimplicit-fallthrough=5’
Some of those, like the kasan and the mips build errors, have been fixed
in -next. The "unrecognized command line option" is brand new. I did not
have time to look into the others. From a testing perspective this release
was a nightmare: at times there were more than 100 qemu boot test failures
in my tests. Ultimately that means that bisectability will be limited.
Not that it helps, but yesterday the situation looked much better than
today.
Guenter
next prev parent reply other threads:[~2021-11-15 4:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 22:28 Linux 5.16-rc1 Linus Torvalds
2021-11-15 3:17 ` linux-next: stats (Was: Linux 5.16-rc1) Stephen Rothwell
2021-11-15 18:02 ` is arch/h8300 dead, was " Christoph Hellwig
2021-11-15 4:56 ` Guenter Roeck [this message]
2021-11-15 5:21 ` Linux 5.16-rc1 Linus Torvalds
2021-11-15 6:33 ` Guenter Roeck
2021-11-15 17:07 ` Guenter Roeck
2021-11-15 17:53 ` Linus Torvalds
2021-11-15 20:39 ` Nick Terrell
2021-11-15 18:10 ` Linus Torvalds
2021-11-15 18:19 ` Helge Deller
2021-11-15 18:38 ` Guenter Roeck
2021-11-16 11:36 ` Michael Ellerman
2021-11-16 14:50 ` Guenter Roeck
2021-11-17 20:18 ` Geert Uytterhoeven
2021-11-17 23:29 ` Anton Altaparmakov
2021-11-18 0:28 ` Linus Torvalds
2021-11-18 1:26 ` Anton Altaparmakov
2021-11-18 1:54 ` Linus Torvalds
2021-11-18 21:23 ` Guenter Roeck
2021-11-18 22:34 ` Linus Torvalds
2021-11-18 23:08 ` Guenter Roeck
2021-11-15 16:14 ` Geert Uytterhoeven
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=20211115045616.GA1012538@roeck-us.net \
--to=linux@roeck-us.net \
--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).