Project

General

Profile

Bug #18838

valgrind: Leak_StillReachable in libceph-common __tracepoints__init

Added by John Spray 8 months ago. Updated 7 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Code Hygiene
Target version:
-
Start date:
02/06/2017
Due date:
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Release:
Component(FS):
ceph-fuse
Needs Doc:
No

Description

http://pulpito.ceph.com/jspray-2017-02-06_11:13:20-fs-wip-jcsp-testing-20170204-distro-basic-smithi/789908

<error>
  <unique>0x1a</unique>
  <tid>1</tid>
  <kind>Leak_StillReachable</kind>
  <xwhat>
    <text>32 bytes in 1 blocks are still reachable in loss record 27 of 74</text>
    <leakedbytes>32</leakedbytes>
    <leakedblocks>1</leakedblocks>
  </xwhat>
  <stack>
    <frame>
      <ip>0x4C29975</ip>
      <obj>/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so</obj>
      <fn>calloc</fn>
      <dir>/builddir/build/BUILD/valgrind-3.11.0/coregrind/m_replacemalloc</dir>
      <file>vg_replace_malloc.c</file>
      <line>711</line>
    </frame>
    <frame>
      <ip>0xF3DE61F</ip>
      <obj>/usr/lib64/libdl-2.17.so</obj>
      <fn>_dlerror_run</fn>
    </frame>
    <frame>
      <ip>0xF3DE050</ip>
      <obj>/usr/lib64/libdl-2.17.so</obj>
      <fn>dlopen@@GLIBC_2.2.5</fn>
    </frame>
    <frame>
      <ip>0x528A313</ip>
      <obj>/usr/lib64/ceph/libceph-common.so.0</obj>
      <fn>__tracepoints__init</fn>
      <dir>/usr/include/lttng</dir>
      <file>tracepoint.h</file>
      <line>281</line>
    </frame>
    <frame>
      <ip>0x400F1E2</ip>
      <obj>/usr/lib64/ld-2.17.so</obj>
      <fn>_dl_init</fn>
    </frame>
    <frame>
      <ip>0x4001219</ip>
      <obj>/usr/lib64/ld-2.17.so</obj>
    </frame>
    <frame>
      <ip>0x4</ip>
    </frame>
    <frame>
      <ip>0xFFF000C46</ip>
    </frame>
    <frame>
      <ip>0xFFF000C50</ip>
    </frame>
    <frame>
      <ip>0xFFF000C53</ip>
    </frame>
    <frame>
      <ip>0xFFF000C5A</ip>
    </frame>
    <frame>
      <ip>0xFFF000C63</ip>
    </frame>
  </stack>
</error>

This smells a lot like something which should be a suppression. I also notice this is our new ceph-common .so, so it might be related to that change.

History

#1 Updated by Kefu Chai 7 months ago

  • Status changed from New to Need Review
  • Assignee set to Kefu Chai

#2 Updated by John Spray 7 months ago

  • Status changed from Need Review to Resolved

Also available in: Atom PDF