<?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 stack-uar.c</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>21f72c05 - [hwasan] Add __hwasan_add_frame_record to the hwasan interface</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c#21f72c05</link>
        <description>[hwasan] Add __hwasan_add_frame_record to the hwasan interfaceHwasan includes instructions in the prologue that mix the PC and SP and storeit into the stack ring buffer stored at __hwasan_tls. This is a thread_localglobal exposed from the hwasan runtime. However, if TLS-mechanisms or thehwasan runtime haven&apos;t been setup yet, it will be invalid to access __hwasan_tls.This is the case for Fuchsia where we instrument libc, so some functions thatare instrumented but can run before hwasan initialization will incorrectlyaccess this global. Additionally, libc cannot have any TLS variables, so wecannot weakly define __hwasan_tls until the runtime is loaded.A way we can work around this is by moving the instructions into a hwasanfunction that does the store into the ring buffer and creating a weak definitionof that function locally in libc. This way __hwasan_tls will not actually bereferenced. This is not our long-term solution, but this will allow us to rollout hwasan in the meantime.This patch includes:- A new llvm flag for choosing to emit a libcall rather than instructions in the  prologue (off by default)- The libcall for storing into the ringbuffer (__hwasan_add_frame_record)Differential Revision: https://reviews.llvm.org/D128387

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c</description>
        <pubDate>Wed, 13 Jul 2022 22:07:59 +0000</pubDate>
        <dc:creator>Leonard Chan &lt;leonardchan@google.com&gt;</dc:creator>
    </item>
<item>
        <title>d843d5c8 - Revert &quot;[hwasan] Add __hwasan_record_frame_record to the hwasan interface&quot;</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c#d843d5c8</link>
        <description>Revert &quot;[hwasan] Add __hwasan_record_frame_record to the hwasan interface&quot;This reverts commit 4956620387ee45a48a394853a47ddd65195c4cc6.This broke a sanitizer builder: https://lab.llvm.org/buildbot/#/builders/77/builds/19597

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c</description>
        <pubDate>Wed, 13 Jul 2022 22:06:07 +0000</pubDate>
        <dc:creator>Leonard Chan &lt;leonardchan@google.com&gt;</dc:creator>
    </item>
<item>
        <title>49566203 - [hwasan] Add __hwasan_record_frame_record to the hwasan interface</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c#49566203</link>
        <description>[hwasan] Add __hwasan_record_frame_record to the hwasan interfaceHwasan includes instructions in the prologue that mix the PC and SP and storeit into the stack ring buffer stored at __hwasan_tls. This is a thread_localglobal exposed from the hwasan runtime. However, if TLS-mechanisms or thehwasan runtime haven&apos;t been setup yet, it will be invalid to access __hwasan_tls.This is the case for Fuchsia where we instrument libc, so some functions thatare instrumented but can run before hwasan initialization will incorrectlyaccess this global. Additionally, libc cannot have any TLS variables, so wecannot weakly define __hwasan_tls until the runtime is loaded.A way we can work around this is by moving the instructions into a hwasanfunction that does the store into the ring buffer and creating a weak definitionof that function locally in libc. This way __hwasan_tls will not actually bereferenced. This is not our long-term solution, but this will allow us to rollout hwasan in the meantime.This patch includes:- A new llvm flag for choosing to emit a libcall rather than instructions in the  prologue (off by default)- The libcall for storing into the ringbuffer (__hwasan_record_frame_record)Differential Revision: https://reviews.llvm.org/D128387

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c</description>
        <pubDate>Wed, 06 Jul 2022 21:47:43 +0000</pubDate>
        <dc:creator>leonardchan &lt;leonardchan@google.com&gt;</dc:creator>
    </item>
<item>
        <title>b458bb8c - [hwasan] Display causes in order of probability.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c#b458bb8c</link>
        <description>[hwasan] Display causes in order of probability.A heap or global buffer that is far away from the faulting address isunlikely to be the cause, especially if there is a potentialuse-after-free as well, so we want to show it after the othercauses.Reviewed By: eugenisDifferential Revision: https://reviews.llvm.org/D104781

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c</description>
        <pubDate>Mon, 21 Jun 2021 18:55:31 +0000</pubDate>
        <dc:creator>Florian Mayer &lt;fmayer@google.com&gt;</dc:creator>
    </item>
<item>
        <title>0867edfc - [HWASan] Add basic stack tagging support for LAM.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c#0867edfc</link>
        <description>[HWASan] Add basic stack tagging support for LAM.Adds the basic instrumentation needed for stack tagging.Currently does not support stack short granules or TLS stack histories,since a different code path is followed for the callback instrumentationwe use.We may simply wait to support these two features until we switch toa custom calling convention.Patch By: xiangzhangllvm, morehouseReviewed By: vitalybukaDifferential Revision: https://reviews.llvm.org/D102901

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c</description>
        <pubDate>Fri, 11 Jun 2021 15:19:36 +0000</pubDate>
        <dc:creator>Matt Morehouse &lt;mascasa@google.com&gt;</dc:creator>
    </item>
<item>
        <title>772851ca - [HWASan] Disable stack, globals and force callbacks for x86_64.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c#772851ca</link>
        <description>[HWASan] Disable stack, globals and force callbacks for x86_64.Subsequent patches will implement page-aliasing mode for x86_64, whichwill initially only work for the primary heap allocator.  We forcecallback instrumentation to simplify the initial aliasingimplementation.Reviewed By: vitalybuka, eugenisDifferential Revision: https://reviews.llvm.org/D98069

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c</description>
        <pubDate>Mon, 22 Mar 2021 15:01:48 +0000</pubDate>
        <dc:creator>Matt Morehouse &lt;mascasa@google.com&gt;</dc:creator>
    </item>
<item>
        <title>d11ea651 - hwasan: Teach the runtime to identify the local variable being accessed in UAR reports.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c#d11ea651</link>
        <description>hwasan: Teach the runtime to identify the local variable being accessed in UAR reports.Each function&apos;s PC is recorded in the ring buffer. From there we can accessthe function&apos;s local variables and reconstruct the tag of each one with thehelp of the information printed by llvm-symbolizer&apos;s new FRAME command. Wecan then find the variable that was likely being accessed by matching thepointer&apos;s tag against the reconstructed tag.Differential Revision: https://reviews.llvm.org/D63469llvm-svn: 364607

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c</description>
        <pubDate>Thu, 27 Jun 2019 23:16:13 +0000</pubDate>
        <dc:creator>Peter Collingbourne &lt;peter@pcc.me.uk&gt;</dc:creator>
    </item>
<item>
        <title>360163f6 - Fix unsymbolized stack history printing.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c#360163f6</link>
        <description>Fix unsymbolized stack history printing.Summary:When symbols are unavailable, the current code prints  sp: ... pc: ... (null) (null)instead of module name + offset.Change the output to include module name and offset, and also to matchthe regular sanitizer stack trace format so that it is recognized bysymbolize.py out of the box.Reviewers: kcc, pccSubscribers: kubamracek, jdoerfert, llvm-commitsTags: #llvmDifferential Revision: https://reviews.llvm.org/D58267llvm-svn: 354157

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c</description>
        <pubDate>Fri, 15 Feb 2019 18:38:23 +0000</pubDate>
        <dc:creator>Evgeniy Stepanov &lt;eugeni.stepanov@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>a53bb3ac - Fix typo in test cases as well.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c#a53bb3ac</link>
        <description>Fix typo in test cases as well.llvm-svn: 349255

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c</description>
        <pubDate>Sat, 15 Dec 2018 07:08:04 +0000</pubDate>
        <dc:creator>Peter Collingbourne &lt;peter@pcc.me.uk&gt;</dc:creator>
    </item>
<item>
        <title>342ca711 - [hwasan] Fix stack-uar.c after rCRT345110</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c#342ca711</link>
        <description>[hwasan] Fix stack-uar.c after rCRT345110Set -fno-discard-value-names so that the frame description string contains the variable name.llvm-svn: 346120

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c</description>
        <pubDate>Mon, 05 Nov 2018 07:16:25 +0000</pubDate>
        <dc:creator>Fangrui Song &lt;maskray@google.com&gt;</dc:creator>
    </item>
<item>
        <title>ad11526c - [hwasan] when printing a stack-related bugs, also print stack frame descriptions provided by the compiler</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c#ad11526c</link>
        <description>[hwasan] when printing a stack-related bugs, also print stack frame descriptions provided by the compilerllvm-svn: 345110

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c</description>
        <pubDate>Wed, 24 Oct 2018 01:35:50 +0000</pubDate>
        <dc:creator>Kostya Serebryany &lt;kcc@google.com&gt;</dc:creator>
    </item>
<item>
        <title>3d3d9d69 - [hwasan] extend the stack-uar test</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c#3d3d9d69</link>
        <description>[hwasan] extend the stack-uar testllvm-svn: 344213

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c</description>
        <pubDate>Thu, 11 Oct 2018 01:05:18 +0000</pubDate>
        <dc:creator>Kostya Serebryany &lt;kcc@google.com&gt;</dc:creator>
    </item>
<item>
        <title>1ee01bbf - [hwasan] rename two .cc tests into .c</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c#1ee01bbf</link>
        <description>[hwasan] rename two .cc tests into .cllvm-svn: 341739

            List of files:
            /llvm-project-15.0.7/compiler-rt/test/hwasan/TestCases/stack-uar.c</description>
        <pubDate>Sat, 08 Sep 2018 01:27:10 +0000</pubDate>
        <dc:creator>Kostya Serebryany &lt;kcc@google.com&gt;</dc:creator>
    </item>
</channel>
</rss>
