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] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 19 Oct 2021 13:33:20 -0700
From:   Guenter Roeck <>
To:     Linus Torvalds <>
Cc:     Linux Kernel Mailing List <>
Subject: Re: Linux 5.15-rc6

On Sun, Oct 17, 2021 at 08:14:59PM -1000, Linus Torvalds wrote:
> So here we are, slightly later on a Sunday than usual due to travel,
> but rc6 is out.
> I'd love to say that it's all looking average, but rc6 is actually
> bigger han rc5 was, and larger than normal for this time in the
> release cycle.
> It's not _enormously_ larger than normal, and it's not the largest rc6
> we've had, but it's still slightly worrisome. By rc6 I really do
> expect things to have started calming down.
> I'm hoping it's just one of those random timing effects, with a couple
> of slightly bigger pulls having come in the last week, and we'll see
> the next week being extra quiet because rc6 got some of the stuff that
> would normally have hit rc7. It happens. But let's see how this goes.
> The 5.15 cycle over-all remains one of the smaller cycles (at least
> counting commits), so I wouldn't have expected this to be one that
> requires an extra rc, but that may be what ends up happening unless
> the upcoming week is really nice and calm.
> That said, nothing in here looks _particularly_ worrisome. It really
> smells like just random timing effects to me, with networking, GPU
> drivers, and ntfs3 all having had a somewhat active week.  Other than
> that it all really looks fairly normal.
> Full details in the shortlog below.
> Please give it a whirl. And let's hope for a nice calm next week and a
> smaller rc7.

Build results:
	total: 153 pass: 149 fail: 4
Failed builds:
Qemu test results:
	total: 480 pass: 480 fail:

The error is:

Building alpha:allmodconfig ... failed
Error log:
<stdin>:1517:2: warning: #warning syscall clone3 not implemented [-Wcpp]
drivers/spi/spi-tegra20-slink.c:1197:12: error: 'tegra_slink_runtime_resume' defined but not used [-Werror=unused-function]
 1197 | static int tegra_slink_runtime_resume(struct device *dev)

This was introduced by a bad conflict resolution between the following
two patches.

efafec27c565 spi: Fix tegra20 build with CONFIG_PM=n
2bab94090b01 spi: tegra20-slink: Declare runtime suspend and resume functions conditionally

The fix is at
and queued in -next.


Powered by blists - more mailing lists