linux-kernel - Re: stable-rc build: 6 warnings 0 failures (stable-rc/v3.18.72-22-g11fceae)

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]

Message-ID: <CAK8P3a2N7t1TOhkx2JMJMA11m8KhZrXPmr1hbonhCujz4N+EGQ@mail.gmail.com>
Date:   Fri, 6 Oct 2017 11:47:45 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     gregkh <gregkh@...uxfoundation.org>
Cc:     "Olof's autobuilder" <build@...om.net>,
        stable <stable@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Olof Johansson <olof@...om.net>,
        Kernel Build Reports Mailman List 
        <kernel-build-reports@...ts.linaro.org>
Subject: Re: stable-rc build: 6 warnings 0 failures (stable-rc/v3.18.72-22-g11fceae)

On Fri, Oct 6, 2017 at 11:23 AM, gregkh <gregkh@...uxfoundation.org> wrote:
> On Fri, Oct 06, 2017 at 11:12:32AM +0200, Arnd Bergmann wrote:
>> On Thu, Oct 5, 2017 at 11:16 AM, gregkh <gregkh@...uxfoundation.org> wrote:
>> >
>> > Thanks for these, all now queued up.
>>
>> It looks like you applied them to 4.4.y and 4.9.y, but not to 3.18.y, which
>> still shows both problems in the 3.18.73 build report.
>>
>> Can you check again?
>
> I see them in my patch queue, where are you looking?  Let me push out
> the next 3.18.y-rc release so you can check easier...

I was looking at the build results from Olof's build bot 16 hours ago.
I was confused by the fact that the build result arrived here after your
mail saying you merged the fix, but this is obviously explained by
way you pushed out the release branch to the stable-rc before merging,
and the delay on the build bot.

It's all there, and I now understand where to look next time, thanks!

     Arnd