linux-kernel - Re: [GIT PULL] locking changes for v4.15

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: <CA+55aFzyVnKKqZZSjn17m9hc7e7be2NG5-W1fGRrxXO63_+MyQ@mail.gmail.com>
Date:   Mon, 13 Nov 2017 12:42:44 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Ingo Molnar <mingo@...nel.org>,
        Heiko Carstens <heiko.carstens@...ibm.com>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Peter Zijlstra <a.p.zijlstra@...llo.nl>,
        "Paul E. McKenney" <paulmck@...ibm.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] locking changes for v4.15

On Sun, Nov 12, 2017 at 11:31 PM, Ingo Molnar <mingo@...nel.org> wrote:
>
> Please pull the latest locking-core-for-linus git tree from:

Ok, this clashed pretty badly with the s390 update which had big
locking changes to use the generic code.

I tried to fix it all up, and maybe it's even ok. But it's also
entirely possible that I messed something up badly, and I don't have
an s390 build environment, so please, Heiko, can you look at the
result and send me any necessary fixes?

(I haven't pushed out yet, my own private build check is still going,
but it should be out soon assuming I didn't miss something _else_
too..)

                 Linus