Actions
Bug #36033
closedmon: valgrind leaks from rte_log_init()
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
dpdk mon
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
The rgw suite is seeing a lot of these valgrind issues from ceph-mon:
<error> <unique>0x12</unique> <tid>1</tid> <kind>Leak_StillReachable</kind> <xwhat> <text>249 bytes in 29 blocks are still reachable in loss record 19 of 27</text> <leakedbytes>249</leakedbytes> <leakedblocks>29</leakedblocks> </xwhat> <stack> <frame> <ip>0x4C29C23</ip> <obj>/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so</obj> <fn>malloc</fn> <dir>/builddir/build/BUILD/valgrind-3.13.0/coregrind/m_replacemalloc</dir> <file>vg_replace_malloc.c</file> <line>299</line> </frame> <frame> <ip>0x117A0809</ip> <obj>/usr/lib64/libc-2.17.so</obj> <fn>strdup</fn> </frame> <frame> <ip>0x2A99C4</ip> <obj>/usr/bin/ceph-mon</obj> <fn>rte_log_init</fn> </frame> <frame> <ip>0x835DAC</ip> <obj>/usr/bin/ceph-mon</obj> <fn>__libc_csu_init</fn> </frame> <frame> <ip>0x117363D4</ip> <obj>/usr/lib64/libc-2.17.so</obj> <fn>(below main)</fn> </frame> </stack> </error>
from http://pulpito.ceph.com/teuthology-2018-09-15_03:05:01-rgw-master-distro-basic-smithi/
They're coming from dpdk, presumably before main(), so I can only assume this is somehow related to linkage.
Updated by Kefu Chai over 5 years ago
Updated by Sage Weil about 3 years ago
- Status changed from In Progress to Closed
Actions