linux-kernel - Re: [PATCH 4.14 000/193] 4.14.3-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] [day] [month] [year] [list]

Date:   Thu, 30 Nov 2017 16:29:31 -0800
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,
        shuahkh@....samsung.com, patches@...nelci.org,
        ben.hutchings@...ethink.co.uk, lkft-triage@...ts.linaro.org,
        stable@...r.kernel.org, kernelci@...e-electrons.com
Subject: Re: [PATCH 4.14 000/193] 4.14.3-stable review

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

> On Tue, Nov 28, 2017 at 07:23:57AM -0800, kernelci.org bot wrote:
>> stable-rc/linux-4.14.y boot: 239 boots: 11 failed, 197 passed with 31 offline (v4.14.2-194-g9ff910a1edbf)
>> 
>> Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.14.2-194-g9ff910a1edbf/
>> Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.14.y/kernel/v4.14.2-194-g9ff910a1edbf/
>> 
>> Tree: stable-rc
>> Branch: linux-4.14.y
>> Git Describe: v4.14.2-194-g9ff910a1edbf
>> Git Commit: 9ff910a1edbfe3044963b615a4fb2d29f611579d
>> Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>> Tested: 94 unique boards, 24 SoC families, 21 builds out of 189
>> 
>> Boot Regressions Detected:
>> 
>> arm:
>> 
>>     at91_dt_defconfig:
>>         at91rm9200ek_rootfs:nfs:
>>             lab-free-electrons: failing since 1 day (last pass: v4.14.2 - first fail: v4.14.2-181-g684cdd60a58a)
>> 
>>     sunxi_defconfig:
>>         sun5i-gr8-chip-pro:
>>             lab-free-electrons: new failure (last pass: v4.14.2-181-g684cdd60a58a)
>> 
>> arm64:
>> 
>>     defconfig:
>>         meson-gxl-s905d-p230:
>>             lab-baylibre-seattle: new failure (last pass: v4.14.2-181-g684cdd60a58a)
>>         meson-gxl-s905x-khadas-vim:
>>             lab-baylibre-seattle: new failure (last pass: v4.14.2-181-g684cdd60a58a)
>>         meson-gxl-s905x-nexbox-a95x:
>>             lab-baylibre-seattle: new failure (last pass: v4.14.2-181-g684cdd60a58a)
>>         meson-gxl-s905x-p212:
>>             lab-baylibre-seattle: new failure (last pass: v4.14.2-181-g684cdd60a58a)
>> 
>>     defconfig+CONFIG_LKDTM=y:
>>         meson-gxl-s905d-p230:
>>             lab-baylibre-seattle: new failure (last pass: v4.14.2-181-g684cdd60a58a)
>>         meson-gxl-s905x-khadas-vim:
>>             lab-baylibre-seattle: new failure (last pass: v4.14.2-181-g684cdd60a58a)
>>         meson-gxl-s905x-p212:
>>             lab-baylibre-seattle: new failure (last pass: v4.14.2-181-g684cdd60a58a)
>
> That's a lot of new failures, did I break something?
>

Nope, most of it was a lab config in my lab.

One of the patches I requested for stable added a reserved memory region
which conflicted with how my lab was loading the initrd, causing all of
those meson-* failures in my lab.

As Mark pointed out, a subsequent linux-4.14.y build booted fine on all
those boards.

The lab-free-electrons failures aren't now, and they (now Cc'd) are looking into
those (I hope.)

Kevin