From: Christophe Varoqui <christophe.varoqui@free.fr>
To: bmarzins@redhat.com
Cc: dm-devel@redhat.com
Subject: multipathd leak
Date: Thu, 27 Oct 2005 12:14:23 +0200 [thread overview]
Message-ID: <20051027101423.GA19853@free.fr> (raw)
Hello,
can you look into this leak reported by valgrind :
(valgrind --show-reachable=yes --leak-check=full -v multipathd/multipathd -d)
==2957== 16384 bytes in 1 blocks are definitely lost in loss record 10 of 10
==2957== at 0x11B1BE96: malloc (vg_replace_malloc.c:149)
==2957== by 0x11D41B61: dm_task_run (in /lib/libdevmapper.so.1.01)
==2957== by 0x40444D: waiteventloop (main.c:481)
==2957== by 0x40464C: waitevent (main.c:537)
==2957== by 0x11C2FB1B: start_thread (in /lib/libpthread-2.3.5.so)
==2957== by 0x1243B272: clone (in /lib/libc-2.3.5.so)
We miss a dm_task_destroy in the stop_waiter_thread path.
It seems related to the pthread_kill trickery you are familiar with.
Didn't we conclude the trickery was due to a glibc bug earlier ?
If so, can this be fixed in updates or will it have to wait till RHEL5 ?
Regards,
cvaroqui
reply other threads:[~2005-10-27 10:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051027101423.GA19853@free.fr \
--to=christophe.varoqui@free.fr \
--cc=bmarzins@redhat.com \
--cc=dm-devel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.