linux-kernel - Re: next-20170217 boot on POWER8 LPAR : WARNING @kernel/jump

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: <20170227102243.2172a8ea@gandalf.local.home>
Date:   Mon, 27 Feb 2017 10:22:43 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Jason Baron <jbaron@...mai.com>
Cc:     Sachin Sant <sachinp@...ux.vnet.ibm.com>,
        linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
        linuxppc-dev@...abs.org, Michael Ellerman <mpe@...erman.id.au>
Subject: Re: next-20170217 boot on POWER8 LPAR : WARNING
 @kernel/jump_label.c:287

On Tue, 21 Feb 2017 11:37:21 -0500
Jason Baron <jbaron@...mai.com> wrote:

> Thanks for testing. We probably need something like the following to 
> make sure we don't hit this on other arches. Steve - I will send 4 
> separate patches for this to get arch maintainers' acks for this?
> 

I just got back from ELC, so sorry for the late reply.

I think you can just send this as one patch, as it is a single fix. Cc
each of the arch maintainers though. Unless you think it will have
conflicts with other changes in those archs. But I'm assuming there
wont be any conflicts.

This is a fix for something that I just pushed to Linus, thus it can
still get in after the merge window closes.

-- Steve