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]
Date:   Sat, 08 Oct 2016 02:53:22 -0700
From:   Kevin Hilman <khilman@...libre.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     "kernelci.org bot" <bot@...nelci.org>,
        linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
        akpm@...ux-foundation.org, linux@...ck-us.net,
        shuah.kh@...sung.com, patches@...nelci.org,
        ben.hutchings@...ethink.co.uk, stable@...r.kernel.org,
        antoine.tenart@...e-electrons.com,
        quentin.schulz@...e-electrons.com,
        thomas.petazzoni@...e-electrons.com
Subject: Re: [PATCH 4.4 00/93] 4.4.24-stable review

Greg Kroah-Hartman <gregkh@...uxfoundation.org> writes:

> On Fri, Oct 07, 2016 at 04:06:04AM -0700, kernelci.org bot wrote:
>> stable-rc boot: 164 boots: 1 failed, 158 passed with 5 offline (v4.4.23-94-g5dba8e95fccc)
>> 
>> Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/kernel/v4.4.23-94-g5dba8e95fccc/
>> Full Build Summary: https://kernelci.org/build/stable-rc/kernel/v4.4.23-94-g5dba8e95fccc/
>> 
>> Tree: stable-rc
>> Branch: local/linux-4.4.y
>> Git Describe: v4.4.23-94-g5dba8e95fccc
>> Git Commit: 5dba8e95fccc45d6934b70128e6ce72e4cbc44e1
>> Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>> Tested: 41 unique boards, 13 SoC families, 22 builds out of 201
>> 
>> Boot Failure Detected: https://kernelci.org/boot/?v4.4.23-94-g5dba8e95fccc&fail
>> 
>> arm:
>> 
>>     multi_v7_defconfig+CONFIG_PROVE_LOCKING=y:
>>         at91-sama5d3_xplained: 1 failed lab
>
> Yeah, same failure!
>
> thanks for the report,

Pretty sure this one is related to the bootloader settings not properly
dealing with the larger image size created by CONFIG_PROVE_LOCKING=y,
but still waiting for the Free Electrons guys (cc'd) to have a closer look.

Kevin


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ