linux-kernel - Re: [PATCH v4 0/4] linkage: better symbol aliasing

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]

Date:   Thu, 17 Feb 2022 11:58:31 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     Mark Rutland <mark.rutland@....com>
Cc:     linux-kernel@...r.kernel.org, catalin.marinas@....com,
        will@...nel.org, acme@...hat.com, ardb@...nel.org, bp@...en8.de,
        broonie@...nel.org, dave.hansen@...ux.intel.com,
        joey.gouly@....com, jpoimboe@...hat.com, jslaby@...e.cz,
        linux-arm-kernel@...ts.infradead.org, mingo@...hat.com,
        tglx@...utronix.de
Subject: Re: [PATCH v4 0/4] linkage: better symbol aliasing

On Wed, Feb 16, 2022 at 04:22:25PM +0000, Mark Rutland wrote:
> Catalin, Will, Peter: I think this is ready now and would like to get it
> queued, but it looks like this may (trivially) conflict with other bits
> we'll want to queue in either the arm64 tree (Joey's string routine
> changes [4]), or tip tree (Peter's IBT series).
> 
> I assume the best thing to do would be to have a stable branch merged in
> both of those. I've tagged this such that it can be pulled (details
> below); Peter also suggested he could make a stable branch in the tip
> tree. Any preference?

No real preference, The conflicts on my end are really rather trivial
IIRC, but they're a nice clean-up.

If I don't take then, feel free to add:

Acked-by: Peter Zijlstra (Intel) <peterz@...radead.org>