linux-kernel - Re: [PATCH 4.16 000/110] 4.16.11-stable review

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] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 22 May 2018 06:35:27 -0700
From:   Guenter Roeck <linux@...ck-us.net>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org
Cc:     torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
        shuah@...nel.org, patches@...nelci.org,
        ben.hutchings@...ethink.co.uk, lkft-triage@...ts.linaro.org,
        stable@...r.kernel.org
Subject: Re: [PATCH 4.16 000/110] 4.16.11-stable review

On 05/21/2018 02:10 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.16.11 release.
> There are 110 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
> 
> Responses should be made by Tue May 22 21:04:14 UTC 2018.
> Anything received after that time might be too late.
> 

Build results:
	total: 143 pass: 141 fail: 2
Failed builds:
um:defconfig
xtensa:allmodconfig
Qemu test results:
total: 139 pass: 139 fail: 0

The um build failure is transient; it applies to all recent releases,
including upstream. Rebuilding usually solves it, and indeed solved it
here as  well. I am listing it to make people aware of it; maybe someone
has an idea how to fix it.

Building um:defconfig ... failed
--------------
Error log:
make[2]: *** No rule to make target 'archheaders'.  Stop.
make[1]: *** [archheaders] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [sub-make] Error 2
--------------

The xtensa build failure has been fixed upstream with commit
e3ca34880652 ("net/mlx5: Fix build break when CONFIG_SMP=n").

Details are available at http://kerneltests.org/builders/.

Guenter