Re: Linux 5.14-rc1

[Guenter Roeck]

On Sun, Jul 11, 2021 at 03:49:31PM -0700, Linus Torvalds wrote:
> You all know the drill by now. It's been the usual two weeks of merge
> window, and not it's closed, and 5.14-rc1 is out there.
> 
[ ... [ 
> Please do test, and we can get the whole calming-down period rolling
> and hopefully get a timely final 5.14 release.
> 

Build results:
	total: 154 pass: 152 fail: 2
Failed builds:
	arcv2:allnoconfig
	riscv:allmodconfig
Qemu test results:
	total: 462 pass: 443 fail: 19
Failed tests:
	arm:z2:pxa_defconfig:nodebug:nocd:nofs:nonvme:noscsi:notests:novirt:nofdt:flash8,384k,2:rootfs
	<all riscv32>

z2:pxa_defconfig fails to boot due to commit 4b361cfa8624 ("mtd: core:
add OTP nvmem provider support"). A patch to fix the problem has been
posted at
https://patchwork.ozlabs.org/project/linux-mtd/patch/20210707135359.32398-1-michael@xxxxxxxx/

The riscv:allmodconfig build failure is not new. It is seen if both
STACKPROTECTOR_PER_TASK and GCC_PLUGIN_RANDSTRUCT are enabled.
See
https://patchwork.kernel.org/project/linux-riscv/patch/20210706162621.940924-1-linux@xxxxxxxxxxxx/
for details and a proposed fix.

riscv32 images fail to boot due to commit ca6eaaa210de ("riscv:
__asm_copy_to-from_user: Optimize unaligned memory access and pipeline
stall"). I reported this a couple of days ago, but have not seen a reply.

In addition to that, there are some new warning tracebacks.

WARNING: CPU: 0 PID: 55 at crypto/testmgr.c:5652 alg_test.part.0+0x148/0x460
self-tests for drbg_nopr_hmac_sha512 (stdrng) failed (rc=-22)

This is due to commits

9b7b94683a9b crypto: DRBG - switch to HMAC SHA512 DRBG as default DRBG
8833272d876e crypto: drbg - self test for HMAC(SHA-512)

which set the default crypto algorithm to SHA-512 without actually
mandating CONFIG_CRYPTO_SHA512. A patch to fix this has been posted at
https://patchwork.kernel.org/project/linux-crypto/patch/304ee0376383d9ceecddbfd216c035215bbff861.camel@xxxxxxxxxx/

WARNING: CPU: 0 PID: 24 at block/genhd.c:484 __device_add_disk+0x248/0x286

This is seen with riscv64 images when booting from usb or scsi drives.
I don't recall seeing this warning before, but I may have missed it
in the flurry of other warnings. It may have been introduced with commit
7c3f828b522b0 ("block: refactor device number setup in __device_add_disk")
but I did not try to bisect it yet.

Guenter