<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Re:Core dump caused by multi-threaded ecall in Intel® Software Guard Extensions (Intel® SGX)</title>
    <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Core-dump-caused-by-calling-ecall-multiple-times/m-p/1188656#M3774</link>
    <description>&lt;P&gt;I did a test, but I just found the error after calling ecall repeatedly.&lt;/P&gt;
&lt;P&gt;I have a question. What are the effects of setting TCSpolicy to 0 and what are the security risks?&lt;/P&gt;
&lt;P&gt;ecall like:&lt;/P&gt;
&lt;DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;void&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;ecall_&lt;/SPAN&gt;&lt;SPAN&gt;srd_increase&lt;/SPAN&gt;&lt;SPAN&gt;(&lt;/SPAN&gt;&lt;SPAN&gt;const&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;char&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;*&lt;/SPAN&gt;&lt;SPAN&gt;path&lt;/SPAN&gt;&lt;SPAN&gt;)&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;{&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; return;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;}&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;trusted {&lt;BR /&gt;public void ecall_srd_increase([in, string] const char* path);&lt;BR /&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;}&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;</description>
    <pubDate>Wed, 01 Jul 2020 06:41:32 GMT</pubDate>
    <dc:creator>LowEntropyBody</dc:creator>
    <dc:date>2020-07-01T06:41:32Z</dc:date>
    <item>
      <title>Core dump caused by calling ecall multiple times</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Core-dump-caused-by-calling-ecall-multiple-times/m-p/1187950#M3760</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I repeatedly call an ecall function. No operation was performed in the function, just return. At the beginning, it went smoothly, but after a while, a core dump occurred. After setting the HeapMaxSize in the configuration to be large, the error time is pushed back. Is there something left in sgx after ecall ends, causing memory overflow? Or is there any way I can solve this problem.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;PS：&lt;/P&gt;
&lt;P&gt;&amp;lt;EnclaveConfiguration&amp;gt;&lt;BR /&gt;&amp;lt;ProdID&amp;gt;0&amp;lt;/ProdID&amp;gt;&lt;BR /&gt;&amp;lt;ISVSVN&amp;gt;0&amp;lt;/ISVSVN&amp;gt;&lt;BR /&gt;&amp;lt;!-- 64M --&amp;gt;&lt;BR /&gt;&amp;lt;StackMaxSize&amp;gt;0x4000000&amp;lt;/StackMaxSize&amp;gt;&lt;BR /&gt;&amp;lt;HeapMaxSize&amp;gt;0x4000000&amp;lt;/HeapMaxSize&amp;gt;&lt;BR /&gt;&amp;lt;TCSNum&amp;gt;20&amp;lt;/TCSNum&amp;gt;&lt;BR /&gt;&amp;lt;TCSPolicy&amp;gt;1&amp;lt;/TCSPolicy&amp;gt;&lt;BR /&gt;&amp;lt;!-- Recommend changing 'DisableDebug' to 1 to make the enclave undebuggable for enclave release --&amp;gt;&lt;BR /&gt;&amp;lt;DisableDebug&amp;gt;0&amp;lt;/DisableDebug&amp;gt;&lt;BR /&gt;&amp;lt;MiscSelect&amp;gt;0&amp;lt;/MiscSelect&amp;gt;&lt;BR /&gt;&amp;lt;MiscMask&amp;gt;0xFFFFFFFF&amp;lt;/MiscMask&amp;gt;&lt;BR /&gt;&amp;lt;/EnclaveConfiguration&amp;gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Update:&lt;/P&gt;
&lt;P&gt;When I set&amp;nbsp;TCSPolicy = 0, this core dump issue will not occur&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jun 2020 09:19:30 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Core-dump-caused-by-calling-ecall-multiple-times/m-p/1187950#M3760</guid>
      <dc:creator>LowEntropyBody</dc:creator>
      <dc:date>2020-06-29T09:19:30Z</dc:date>
    </item>
    <item>
      <title>Re:Core dump caused by multi-threaded ecall</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Core-dump-caused-by-calling-ecall-multiple-times/m-p/1188190#M3762</link>
      <description>&lt;P&gt;Hello LowEntropyBody,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;We are looking into your issue. Please stay tuned.&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 30 Jun 2020 01:25:32 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Core-dump-caused-by-calling-ecall-multiple-times/m-p/1188190#M3762</guid>
      <dc:creator>JesusG_Intel</dc:creator>
      <dc:date>2020-06-30T01:25:32Z</dc:date>
    </item>
    <item>
      <title>Re:Core dump caused by multi-threaded ecall</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Core-dump-caused-by-calling-ecall-multiple-times/m-p/1188590#M3771</link>
      <description>&lt;P&gt;Hello LowEntropyBody,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Since you solved your problem by setting TCSPolicy to 0, do you still need help with this issue?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;If you still need help, please send your source code so we can reproduce your issue.&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 30 Jun 2020 23:56:21 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Core-dump-caused-by-calling-ecall-multiple-times/m-p/1188590#M3771</guid>
      <dc:creator>JesusG_Intel</dc:creator>
      <dc:date>2020-06-30T23:56:21Z</dc:date>
    </item>
    <item>
      <title>Re: Re:Core dump caused by multi-threaded ecall</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Core-dump-caused-by-calling-ecall-multiple-times/m-p/1188656#M3774</link>
      <description>&lt;P&gt;I did a test, but I just found the error after calling ecall repeatedly.&lt;/P&gt;
&lt;P&gt;I have a question. What are the effects of setting TCSpolicy to 0 and what are the security risks?&lt;/P&gt;
&lt;P&gt;ecall like:&lt;/P&gt;
&lt;DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;void&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;ecall_&lt;/SPAN&gt;&lt;SPAN&gt;srd_increase&lt;/SPAN&gt;&lt;SPAN&gt;(&lt;/SPAN&gt;&lt;SPAN&gt;const&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;char&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;*&lt;/SPAN&gt;&lt;SPAN&gt;path&lt;/SPAN&gt;&lt;SPAN&gt;)&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;{&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; return;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;}&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;trusted {&lt;BR /&gt;public void ecall_srd_increase([in, string] const char* path);&lt;BR /&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;}&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Wed, 01 Jul 2020 06:41:32 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Core-dump-caused-by-calling-ecall-multiple-times/m-p/1188656#M3774</guid>
      <dc:creator>LowEntropyBody</dc:creator>
      <dc:date>2020-07-01T06:41:32Z</dc:date>
    </item>
    <item>
      <title>Re:Core dump caused by multi-threaded ecall</title>
      <link>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Core-dump-caused-by-calling-ecall-multiple-times/m-p/1188818#M3779</link>
      <description>&lt;P&gt;Hello Yang, please read page 49 of the SGX Developer Guide for more info on the Thread Binding Policy: &lt;A href="https://community.intel.com/legacyfs/online/drupal_files/managed/33/70/intel-sgx-developer-guide.pdf" target="_blank" style="font-size: 12px;"&gt;https://software.intel.com/sites/default/files/managed/33/70/intel-sgx-developer-guide.pdf&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 01 Jul 2020 18:47:18 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Software-Guard-Extensions/Core-dump-caused-by-calling-ecall-multiple-times/m-p/1188818#M3779</guid>
      <dc:creator>JesusG_Intel</dc:creator>
      <dc:date>2020-07-01T18:47:18Z</dc:date>
    </item>
  </channel>
</rss>

