linux-kernel - Re: [PATCH 3.16 000/217] 3.16.35-rc1 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]

Message-ID: <5722E039.7050505@roeck-us.net>
Date:	Thu, 28 Apr 2016 21:16:57 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Ben Hutchings <ben@...adent.org.uk>, linux-kernel@...r.kernel.org,
	stable@...r.kernel.org
Cc:	torvalds@...ux-foundation.org, Phil Jensen <pjensen@...rnote.com>,
	akpm@...ux-foundation.org
Subject: Re: [PATCH 3.16 000/217] 3.16.35-rc1 review

On 04/26/2016 04:02 PM, Ben Hutchings wrote:
> This is the start of the stable review cycle for the 3.16.35 release.
> There are 217 patches in this series, which will be posted as responses
> to this one.  If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Sat Apr 30 22:00:00 UTC 2016.
> Anything received after that time might be too late.
>

Updated build and test results:

Build results:
	total: 137 pass: 135 fail: 2
Failed builds:
	arc:allnoconfig
	arm64:allmodconfig

Qemu test results:
	total: 97 pass: 94 fail: 3
Failed tests:
	arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zc706
	arm64:smp:defconfig
	arm64:nosmp:defconfig

This is after dropping a couple of builds and qemu tests which are
known to be bad in 3.16, and after some fixes in the tree.

The arm64 build failure is due to gcc5, which needs a patch from a
later kernel. The other failures are new and did not occur in 3.16.7.

A bisect of the arm64 qemu failure points to commit f98ab7a1e78
("mm, vmstat: allow WQ concurrency to discover memory reclaim doesn't
make any progress"). Unfortunately, that is inconclusive, since there
have been several follow-up commits trying to fix it. After reverting
all those commits, the test still fails.

Guenter