linux-kernel - Re: [PATCH 5.8 000/186] 5.8.8-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]

Date:   Wed, 9 Sep 2020 09:47:05 -0700
From:   Guenter Roeck <linux@...ck-us.net>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     linux-kernel@...r.kernel.org, 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 5.8 000/186] 5.8.8-rc1 review

On Tue, Sep 08, 2020 at 05:22:22PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.8.8 release.
> There are 186 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 Thu, 10 Sep 2020 15:21:57 +0000.
> Anything received after that time might be too late.
> 

Build results:
	total: 154 pass: 153 fail: 1
Failed builds:
	powerpc:allmodconfig
Qemu test results:
	total: 430 pass: 430 fail: 0

The powerpc problem is the same as before:

Inconsistent kallsyms data
Try make KALLSYMS_EXTRA_PASS=1 as a workaround

KALLSYMS_EXTRA_PASS=1 doesn't help. The problem is sporadic, elusive, and all
but impossible to bisect. The same build passes on another system, for example,
with a different load pattern. It may pass with -j30 and fail with -j40.
The problem started at some point after v5.8, and got worse over time; by now
it almost always happens. I'd be happy to debug if there is a means to do it,
but I don't have an idea where to even start. I'd disable KALLSYMS in my
test configurations, but the symbol is selected from various places and thus
difficult to disable. So unless I stop building ppc:allmodconfig entirely
we'll just have to live with the failure.

Tested-by: Guenter Roeck <linux@...ck-us.net>

Guenter