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  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:   Wed, 6 May 2020 15:55:02 +0200
From:   Peter Zijlstra <>
To:     Mathieu Desnoyers <>
Cc:     ndesaulniers <>,
        Linus Torvalds <>,
        Rasmus Villemoes <>,
        x86 <>,
        linux-kernel <>,
        rostedt <>,
        Masami Hiramatsu <>,
        bristot <>, jbaron <>,
        Thomas Gleixner <>,
        Ingo Molnar <>, Nadav Amit <>,
        "H. Peter Anvin" <>,
        Andy Lutomirski <>,
        Ard Biesheuvel <>,
        Josh Poimboeuf <>,
        Paolo Bonzini <>,
        "H.J. Lu" <>,
        clang-built-linux <>
Subject: Re: [PATCH v4 14/18] static_call: Add static_cond_call()

On Tue, May 05, 2020 at 04:27:44PM -0400, Mathieu Desnoyers wrote:
> Actually, if the goal is to do code patching of the call, I wonder
> what makes it OK to "guess" all the call patterns generated by the compiler ?

We're not guessing, have have objtool read the compiler output and
record the location for us. The compiler can generate whatever it likes.

Powered by blists - more mailing lists