<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in static_call.c</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2025</copyright>
    <generator>Java</generator><item>
        <title>441c63ff42c4e666304cdd32d23b5fc6bc1ea3cc - Merge tag &apos;arm64-fixes&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux</title>
        <link>http://opengrok.net:8080/history/linux/arch/arm64/kernel/static_call.c#441c63ff42c4e666304cdd32d23b5fc6bc1ea3cc</link>
        <description>Merge tag &apos;arm64-fixes&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linuxPull arm64 fix from Will Deacon: - Implement a basic static call trampoline to fix CFI failures with the   generic implementation* tag &apos;arm64-fixes&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux:  arm64: Use static call trampolines when kCFI is enabled

            List of files:
            /linux/arch/arm64/kernel/static_call.c</description>
        <pubDate>Fri, 03 Apr 2026 15:47:13 +0000</pubDate>
        <dc:creator>Linus Torvalds &lt;torvalds@linux-foundation.org&gt;</dc:creator>
    </item>
<item>
        <title>54ac9ff8f1196afc49d644a1625e0af1c9fcf7f5 - arm64: Use static call trampolines when kCFI is enabled</title>
        <link>http://opengrok.net:8080/history/linux/arch/arm64/kernel/static_call.c#54ac9ff8f1196afc49d644a1625e0af1c9fcf7f5</link>
        <description>arm64: Use static call trampolines when kCFI is enabledImplement arm64 support for the &apos;unoptimized&apos; static call variety, whichroutes all calls through a trampoline that performs a tail call to thechosen function, and wire it up for use when kCFI is enabled. This worksaround an issue with kCFI and generic static calls, where the prototypesof default handlers such as __static_call_nop() and __static_call_ret0()don&apos;t match the expected prototype of the call site, resulting in kCFIfalse positives [0].Since static call targets may be located in modules loaded out of directbranching range, this needs an ADRP/LDR pair to load the branch targetinto R16 and a branch-to-register (BR) instruction to perform anindirect call.Unlike on x86, there is no pressing need on arm64 to avoid indirectcalls at all cost, but hiding it from the compiler as is done here doeshave some benefits:- the literal is located in .rodata, which gives us the same robustness  advantage that code patching does;- no D-cache pollution from fetching hash values from .text sections.From an execution speed PoV, this is unlikely to make any difference atall.Cc: Sami Tolvanen &lt;samitolvanen@google.com&gt;Cc: Sean Christopherson &lt;seanjc@google.com&gt;Cc: Kees Cook &lt;kees@kernel.org&gt;Cc: Peter Zijlstra &lt;peterz@infradead.org&gt;Cc: Will McVicker &lt;willmcvicker@google.com&gt;Reported-by: Carlos Llamas &lt;cmllamas@google.com&gt;Closes: https://lore.kernel.org/all/20260311225822.1565895-1-cmllamas@google.com/ [0]Signed-off-by: Ard Biesheuvel &lt;ardb@kernel.org&gt;Signed-off-by: Will Deacon &lt;will@kernel.org&gt;Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;

            List of files:
            /linux/arch/arm64/kernel/static_call.c</description>
        <pubDate>Tue, 31 Mar 2026 11:04:23 +0000</pubDate>
        <dc:creator>Ard Biesheuvel &lt;ardb@kernel.org&gt;</dc:creator>
    </item>
</channel>
</rss>
