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] [day] [month] [year] [list]
Message-ID: <20210719140437.GA2178213@roeck-us.net>
Date:   Mon, 19 Jul 2021 07:04:37 -0700
From:   Guenter Roeck <linux@...ck-us.net>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 5.14-rc2

On Sun, Jul 18, 2021 at 02:32:31PM -0700, Linus Torvalds wrote:
> Often rc2 ends up being fairly small and calm - either because people
> take a breather after the merge window, or because it takes a while
> for people to start reporting bugs.
> 
> Not so this time.
> 
> At least in pure number of commits, this is the biggest rc2 we've had
> during the 5.x cycle. Whether that is meaningful or not, who knows -
> it might be just random timing effects, or it might indicate that this
> release is not going to be one of those nice and calm ones. We'll just
> have to wait and see.
> 
> But it's not like anything looks super-scary, and it really is too
> early to start worrying about it, so let's just say that rc2's are
> usually smaller than this, and just leave it at that.
> 
> The changes are a bit all over the map, with gpu and networking driver
> fixes accounting for about half of the patch. But some of that is -
> again - AMD GPU header file noise, so that may not be all that
> important. The rest tends to be a mix of things: filesystem fixes,
> networking, perf tool and selftest fixes, and various random noise.
> 
> While being larger than usual, it's by no means _huge_, and anybody
> who cares about the details can easily scan the appended shortlog.
> 

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

No major change here, except that arcv2 images now build.
For reference, the riscv build problem is:

cc1: error: '4496' is not a valid offset in '-mstack-protector-guard-offset='

The patch fixing the arm boot problem is queued in pending-fixes.

There is still the warning about missing sha512 code.

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

The patch fixing this problem is queued in linux-next.

Guenter

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ