public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: zkabelac@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2 ./WHATS_NEW daemons/dmeventd/plugins/lvm2 ...
Date: Thu, 30 Sep 2010 11:40:00 -0000 [thread overview]
Message-ID: <20100930114015.19637.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: zkabelac@sourceware.org 2010-09-30 11:40:14
Modified files:
. : WHATS_NEW
daemons/dmeventd/plugins/lvm2: dmeventd_lvm.c
Log message:
Fix leaked pool report
Swap pool destruction order in dmeventd_lvm2_exit() to fix leak report.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1739&r2=1.1740
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/daemons/dmeventd/plugins/lvm2/dmeventd_lvm.c.diff?cvsroot=lvm2&r1=1.4&r2=1.5
--- LVM2/WHATS_NEW 2010/09/30 11:32:40 1.1739
+++ LVM2/WHATS_NEW 2010/09/30 11:40:14 1.1740
@@ -1,5 +1,6 @@
Version 2.02.75 -
=====================================
+ Swap pool destruction order in dmeventd_lvm2_exit() to fix leak report.
Read whole /proc/self/maps file before working with maps entries.
Speed up unquoting of quoted double quotes and backslashes.
Speed up CRC32 calculations by using a larger lookup table.
--- LVM2/daemons/dmeventd/plugins/lvm2/dmeventd_lvm.c 2010/07/09 15:34:41 1.4
+++ LVM2/daemons/dmeventd/plugins/lvm2/dmeventd_lvm.c 2010/09/30 11:40:14 1.5
@@ -131,10 +131,10 @@
if (!--_register_count) {
lvm2_run(_lvm_handle, "_memlock_dec");
- lvm2_exit(_lvm_handle);
- _lvm_handle = NULL;
dm_pool_destroy(_mem_pool);
_mem_pool = NULL;
+ lvm2_exit(_lvm_handle);
+ _lvm_handle = NULL;
}
pthread_mutex_unlock(&_register_mutex);
next reply other threads:[~2010-09-30 11:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 11:40 zkabelac [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-10 23:34 jbrassow
2011-12-22 15:55 zkabelac
2010-03-04 9:56 zkabelac
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=20100930114015.19637.qmail@sourceware.org \
--to=zkabelac@sourceware.org \
--cc=lvm-devel@redhat.com \
--cc=lvm2-cvs@sourceware.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).