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:   Thu, 23 Sep 2021 00:05:58 +0300
From:   "Kirill A. Shutemov" <>
To:     Borislav Petkov <>
Cc:     Tom Lendacky <>,,,,,,,,,,,,,,
        Brijesh Singh <>,
        Joerg Roedel <>,
        Andi Kleen <>,
        Sathyanarayanan Kuppuswamy 
        Tianyu Lan <>,
        Christoph Hellwig <>,
        Thomas Gleixner <>,
        Ingo Molnar <>,
        Dave Hansen <>,
        Andy Lutomirski <>,
        Peter Zijlstra <>,
        Will Deacon <>
Subject: Re: [PATCH v3 5/8] x86/sme: Replace occurrences of sme_active() with

On Wed, Sep 22, 2021 at 09:52:07PM +0200, Borislav Petkov wrote:
> On Wed, Sep 22, 2021 at 05:30:15PM +0300, Kirill A. Shutemov wrote:
> > Not fine, but waiting to blowup with random build environment change.
> Why is it not fine?
> Are you suspecting that the compiler might generate something else and
> not a rip-relative access?

Yes. We had it before for __supported_pte_mask and other users of

See for instance 4a09f0210c8b ("x86/boot/64/clang: Use fixup_pointer() to
access '__supported_pte_mask'")

Unless we find other way to guarantee RIP-relative access, we must use
fixup_pointer() to access any global variables.

 Kirill A. Shutemov

Powered by blists - more mailing lists