linux-kernel - Re: [PATCH v7 05/28] x86/asm/entry: annotate THUNKs

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: <37e83ece-28c0-a7ec-86a3-b9b5ca2c61f6@suse.cz>
Date:   Tue, 12 Feb 2019 12:51:08 +0100
From:   Jiri Slaby <jslaby@...e.cz>
To:     Borislav Petkov <bp@...en8.de>
Cc:     mingo@...hat.com, linux-arch@...r.kernel.org,
        linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
        "H. Peter Anvin" <hpa@...or.com>, x86@...nel.org
Subject: Re: [PATCH v7 05/28] x86/asm/entry: annotate THUNKs

On 12. 02. 19, 12:46, Borislav Petkov wrote:
> On Tue, Feb 12, 2019 at 12:38:09PM +0100, Jiri Slaby wrote:
>> OK, so I will switch all the *LOCAL* to .L prefix (perhaps as a separate
>> patch prior the series/post the series)?
> 
> Sure.
> 
> I have been doing that off and on but apparently this undertaking
> resembles the whack-a-mole game. :-)

And what if the LOCAL macros prepend .L automatically? The references
would need to be via macro or by manually adding .L. I mean:

SYM_CODE_START_LOCAL(function)
  ret
SYM_CODE_END(function)

And then used as:
call .Lfunction
or
call SYM_LOCAL(function)

Is that too ugly?

thanks,
-- 
js
suse labs