linux-kernel - Re: [RFC PATCH 6/7] static_call: rename EXPORT

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]

Message-ID: <YYrFOZT+6bNTfP+t@hirez.programming.kicks-ass.net>
Date:   Tue, 9 Nov 2021 20:00:09 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     Ard Biesheuvel <ardb@...nel.org>
Cc:     linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        Josh Poimboeuf <jpoimboe@...hat.com>,
        Jason Baron <jbaron@...mai.com>,
        Steven Rostedt <rostedt@...dmis.org>,
        Mark Rutland <mark.rutland@....com>,
        Kees Cook <keescook@...omium.org>
Subject: Re: [RFC PATCH 6/7] static_call: rename EXPORT_ macros to be more
 self-explanatory

On Tue, Nov 09, 2021 at 05:45:48PM +0100, Ard Biesheuvel wrote:
> So let's rename these macros to
> 
>   EXPORT_STATIC_CALL        -> EXPORT_STATIC_CALL_FOR_UPDATE
>   EXPORT_STATIC_CALL_TRAMP  -> EXPORT_STATIC_CALL
> 

Ok, let's pain this shed a bit.

How about:

	EXPORT_STATIC_CALL_RW
	EXPORT_STATIC_CALL_RO

respectively. OR.. alternatively, have both:

	EXPORT_STATIC_CALL_KEY
	EXPORT_STATIC_CALL_TRAMP

and those that want to export both get to use both.