<?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: Kernel 4.19.35 Memory leak when use ping from iputils in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Kernel-4-19-35-Memory-leak-when-use-ping-from-iputils/m-p/985260#M146365</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&amp;nbsp;&lt;A _jive_internal="true" data-content-finding="Community" data-userid="228621" data-username="sebastianpszczolka@gmail.com" href="https://community.nxp.com/people/sebastianpszczolka@gmail.com" style="color: #3d9ce7; background-color: #ffffff; border: 0px; font-weight: 600; text-decoration: underline; font-size: 11.9994px;"&gt;bb bbb&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you let us know the steps you carried out to find the leak? Also can you please mention the EVK that you are using the image?&lt;/P&gt;&lt;P&gt;Also have you tried with tracing with Valgrind?&lt;/P&gt;&lt;P&gt;Below link might help you:&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://github.com/prometheus/node_exporter/issues/825" title="https://github.com/prometheus/node_exporter/issues/825"&gt;Memory leak on iMX.6 · Issue #825 · prometheus/node_exporter · GitHub&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Karan Gajjar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 15 May 2020 07:13:46 GMT</pubDate>
    <dc:creator>karangajjar</dc:creator>
    <dc:date>2020-05-15T07:13:46Z</dc:date>
    <item>
      <title>Kernel 4.19.35 Memory leak when use ping from iputils</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Kernel-4-19-35-Memory-leak-when-use-ping-from-iputils/m-p/985259#M146364</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Good Morning,&lt;/P&gt;&lt;P&gt;When use packet from &lt;STRONG&gt;Yocto&amp;nbsp; Warrior&lt;/STRONG&gt; ip-utils and ping host I see that it eats memory.&lt;/P&gt;&lt;P&gt;After some reserach I found that slab&amp;nbsp;&lt;STRONG&gt;skbuff_head_cache&lt;/STRONG&gt; increase objects in slab alocator:&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;When it works for few hours it runs OOM killer. I checked same packet ping-iputils on x86 and there was no problem.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;How to trace it or fix?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Active / Total Slabs (% used) : 21137 / 53340 (95.9)&lt;BR /&gt; Active / Total Caches (% used) : 1528 / 252867.5%)&lt;BR /&gt; Active / Total Size (% used) : 13447.99K / 8.977.12K (95.0%)&lt;BR /&gt; Minimum / Average / Maximum Object : 04047.230.28K 819.82K (94.8&lt;/P&gt;&lt;P&gt;OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME&lt;BR /&gt; 17416 17345 99% 0.14K 622 28 2488K kernfs_node_cache&lt;BR /&gt; 17416 17345 99% 0.14K 622 28 2488K kernfs_node_cache&lt;BR /&gt; 8820 8806 99% 0.19K 420 21 1680K kmalloc-64&lt;BR /&gt; 6405 6381 99% 0.19K 305 21 1220K dentry&lt;BR /&gt; 4731 4719 99% 0.41K 249 19 1992K inode_cache&lt;BR /&gt; 1648 1588 96% 2.25K 103 15 2412K kmalloc-128&lt;BR /&gt; &lt;STRONG&gt;1476 1466 99% 0.31K 123 12 492K skbuff_head_cache&lt;/STRONG&gt;&lt;BR /&gt; 1140 1133 99% 2.12K 76 15 2432K kmalloc-2048&lt;BR /&gt; 1054 1044 99% 0.12K 31 34 124K buffer_head&lt;BR /&gt; 874 757 86% 0.09K 19 46 76K anon_vma_chain&lt;BR /&gt; 759 751 98% 0.34K 69 11 276K radix_tree_node&lt;BR /&gt; 784 741 94% 0.14K 28 28 112K vm_area_struct&lt;BR /&gt; 648 630 97% 0.62K 54 12 432K kmalloc-512&lt;BR /&gt; 646 630 97% 0.45K 38 17 304K shmem_inode_cache&lt;BR /&gt; 546 546 100% 0.74K 26 21 416K ext4_inode_cache&lt;BR /&gt; 585 508 86% 0.10K 15 39 60K anon_vma&lt;BR /&gt; 506 499 98 done 18 23 22 92K proc_dir_entry&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Feb 2020 15:01:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Kernel-4-19-35-Memory-leak-when-use-ping-from-iputils/m-p/985259#M146364</guid>
      <dc:creator>sebastianpszczo</dc:creator>
      <dc:date>2020-02-05T15:01:33Z</dc:date>
    </item>
    <item>
      <title>Re: Kernel 4.19.35 Memory leak when use ping from iputils</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Kernel-4-19-35-Memory-leak-when-use-ping-from-iputils/m-p/985260#M146365</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&amp;nbsp;&lt;A _jive_internal="true" data-content-finding="Community" data-userid="228621" data-username="sebastianpszczolka@gmail.com" href="https://community.nxp.com/people/sebastianpszczolka@gmail.com" style="color: #3d9ce7; background-color: #ffffff; border: 0px; font-weight: 600; text-decoration: underline; font-size: 11.9994px;"&gt;bb bbb&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you let us know the steps you carried out to find the leak? Also can you please mention the EVK that you are using the image?&lt;/P&gt;&lt;P&gt;Also have you tried with tracing with Valgrind?&lt;/P&gt;&lt;P&gt;Below link might help you:&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://github.com/prometheus/node_exporter/issues/825" title="https://github.com/prometheus/node_exporter/issues/825"&gt;Memory leak on iMX.6 · Issue #825 · prometheus/node_exporter · GitHub&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Karan Gajjar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 May 2020 07:13:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Kernel-4-19-35-Memory-leak-when-use-ping-from-iputils/m-p/985260#M146365</guid>
      <dc:creator>karangajjar</dc:creator>
      <dc:date>2020-05-15T07:13:46Z</dc:date>
    </item>
  </channel>
</rss>

