Actions
Bug #6441
closedmsgr: leak of tls from delay thread
Status:
Can't reproduce
Priority:
High
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Q/A
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
<unique>0x7</unique> <tid>1</tid> <kind>Leak_PossiblyLost</kind> <xwhat> <text>304 bytes in 1 blocks are possibly lost in loss record 6 of 7</text> <leakedbytes>304</leakedbytes> <leakedblocks>1</leakedblocks> </xwhat> <stack> <frame> <ip>0x4C29DB4</ip> <obj>/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so</obj> <fn>calloc</fn> </frame> <frame> <ip>0x4012074</ip> <obj>/lib/x86_64-linux-gnu/ld-2.15.so</obj> <fn>_dl_allocate_tls</fn> <dir>/build/buildd/eglibc-2.15/elf</dir> <file>dl-tls.c</file> <line>297</line> </frame> <frame> <ip>0x503CABC</ip> <obj>/lib/x86_64-linux-gnu/libpthread-2.15.so</obj> <fn>pthread_create@@GLIBC_2.2.5</fn> <dir>/build/buildd/eglibc-2.15/nptl</dir> <file>allocatestack.c</file> <line>571</line> </frame> <frame> <ip>0x9363CA</ip> <obj>/usr/bin/ceph-osd</obj> <fn>Thread::try_create(unsigned long)</fn> <dir>/srv/autobuild-ceph/gitbuilder.git/build/out~/ceph-0.69-365-gefc6b5e/src/common</dir> <file>Thread.cc</file> <line>94</line> </frame> <frame> <ip>0x93647E</ip> <obj>/usr/bin/ceph-osd</obj> <fn>Thread::create(unsigned long)</fn> <dir>/srv/autobuild-ceph/gitbuilder.git/build/out~/ceph-0.69-365-gefc6b5e/src/common</dir> <file>Thread.cc</file> <line>104</line> </frame> <frame> <ip>0xA0A936</ip> <obj>/usr/bin/ceph-osd</obj> <fn>Pipe::maybe_start_delay_thread()</fn> <dir>/srv/autobuild-ceph/gitbuilder.git/build/out~/ceph-0.69-365-gefc6b5e/src/msg</dir> <file>Pipe.cc</file> <line>138</line> </frame> <frame> <ip>0xA111A1</ip> <obj>/usr/bin/ceph-osd</obj> <fn>Pipe::connect()</fn> <dir>/srv/autobuild-ceph/gitbuilder.git/build/out~/ceph-0.69-365-gefc6b5e/src/msg</dir> <file>Pipe.cc</file> <line>1086</line> </frame>
ubuntu@teuthology:/a/sage-c-6/21188
Updated by Sage Weil over 10 years ago
i believe it is the msgr delay injection that triggers this. see the config from the referenced run.
Updated by Sage Weil about 10 years ago
- Status changed from 12 to Can't reproduce
Actions