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:   Mon, 2 May 2022 21:55:25 +0200
From:   Peter Zijlstra <>
To:     Sami Tolvanen <>
Cc:     Kees Cook <>,
        Mark Rutland <>,
        Josh Poimboeuf <>,
        Will Deacon <>,
        Catalin Marinas <>,
        Nathan Chancellor <>,
        Nick Desaulniers <>,
        Joao Moreira <>,
        Sedat Dilek <>,
        Steven Rostedt <>,
        LKML <>, X86 ML <>,,
        linux-arm-kernel <>,
Subject: Re: [RFC PATCH 00/21] KCFI support

On Mon, May 02, 2022 at 08:22:57AM -0700, Sami Tolvanen wrote:

> > Anyway, I think I hate that __builtin, I'd *much* rather see a variable
> > attribute or qualifier for this, such that one can mark a function
> > pointer as not doing CFI.
> >
> > I simply doesn't make sense to have a builtin that operates on an
> > expression. The whole thing is about indirect calls, IOW function
> > pointers.
> I also thought an attribute would be more convenient, but the compiler
> folks prefer a built-in:

That seems to mostly worry about C++ things (overload sets, template
specialization, name mangling) we kernel folks don't seem to much care

I'll stick with saying type system makes more sense to me though.

Powered by blists - more mailing lists