The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@kernel.org>
To: David Laight <david.laight.linux@gmail.com>,
	Marco Elver <elver@google.com>
Cc: linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com
Subject: Re: [PATCH] nios2: Implement _THIS_IP_ using inline asm
Date: Fri, 22 May 2026 07:18:14 -0500	[thread overview]
Message-ID: <56601cbd-99ee-4992-9974-7c25a91c5e0f@kernel.org> (raw)
In-Reply-To: <20260521173336.1465113d@pumpkin>



On 5/21/26 11:33, David Laight wrote:
> On Thu, 21 May 2026 14:23:55 +0200
> Marco Elver <elver@google.com> wrote:
> 
>> Both GCC [1] and Clang [2] consider the generic version of _THIS_IP_ to
>> be broken:
>>
>>          #define _THIS_IP_  ({ __label__ __here; __here: (unsigned long)&&__here; })
>>
>> In particular, the address of a label is only expected to be used with a
>> computed goto.
>>
>> While the generic version more or less works today, it is known to be
>> brittle and may break with current and future optimizations. For
>> example, Clang -O2 always returns 1 when this function is inlined:
>>
>>          static inline unsigned long get_ip(void)
>>          { return ({ __label__ __here; __here: (unsigned long)&&__here; }); }
>>
>> Fix it by overriding _THIS_IP_ in <asm/linkage.h> (which is included by
>> <linux/instruction_pointer.h>) using an architecture-specific inline asm
>> version. Additionally, avoiding taking the address of a label prevents
>> compilers from emitting spurious indirect branch targets (e.g. ENDBR or
>> BTI) under control-flow integrity schemes.
>>
>> Link: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120071 [1]
>> Link: https://github.com/llvm/llvm-project/issues/138272 [2]
>> Signed-off-by: Marco Elver <elver@google.com>
> 
> I know more than enough about the Nios-II instruction set to know it
> is the correct opcode, so:
> 
> Reviewed-by: David Laight <david.laight.linux@gmail.com>
> 
>> ---
>>   arch/nios2/include/asm/linkage.h | 2 ++
>>   1 file changed, 2 insertions(+)
>>

Applied!

Thanks,
Dinh



      reply	other threads:[~2026-05-22 12:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-21 12:23 [PATCH] nios2: Implement _THIS_IP_ using inline asm Marco Elver
2026-05-21 16:33 ` David Laight
2026-05-22 12:18   ` Dinh Nguyen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56601cbd-99ee-4992-9974-7c25a91c5e0f@kernel.org \
    --to=dinguyen@kernel.org \
    --cc=david.laight.linux@gmail.com \
    --cc=elver@google.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox