AnsweredAssumed Answered

Kernel 4.19.35 Memory leak when use ping from iputils

Question asked by bb bbb on Feb 5, 2020
Latest reply on May 15, 2020 by karan gajjar

Good Morning,

When use packet from Yocto  Warrior ip-utils and ping host I see that it eats memory.

After some reserach I found that slab skbuff_head_cache increase objects in slab alocator:

When it works for few hours it runs OOM killer. I checked same packet ping-iputils on x86 and there was no problem.

How to trace it or fix?

Thanks

 

 

Active / Total Slabs (% used) : 21137 / 53340 (95.9)
Active / Total Caches (% used) : 1528 / 252867.5%)
Active / Total Size (% used) : 13447.99K / 8.977.12K (95.0%)
Minimum / Average / Maximum Object : 04047.230.28K 819.82K (94.8

OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME
17416 17345 99% 0.14K 622 28 2488K kernfs_node_cache
17416 17345 99% 0.14K 622 28 2488K kernfs_node_cache
8820 8806 99% 0.19K 420 21 1680K kmalloc-64
6405 6381 99% 0.19K 305 21 1220K dentry
4731 4719 99% 0.41K 249 19 1992K inode_cache
1648 1588 96% 2.25K 103 15 2412K kmalloc-128
1476 1466 99% 0.31K 123 12 492K skbuff_head_cache
1140 1133 99% 2.12K 76 15 2432K kmalloc-2048
1054 1044 99% 0.12K 31 34 124K buffer_head
874 757 86% 0.09K 19 46 76K anon_vma_chain
759 751 98% 0.34K 69 11 276K radix_tree_node
784 741 94% 0.14K 28 28 112K vm_area_struct
648 630 97% 0.62K 54 12 432K kmalloc-512
646 630 97% 0.45K 38 17 304K shmem_inode_cache
546 546 100% 0.74K 26 21 416K ext4_inode_cache
585 508 86% 0.10K 15 39 60K anon_vma
506 499 98 done 18 23 22 92K proc_dir_entry

Outcomes