From: zkabelac@sourceware.org <zkabelac@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 ./WHATS_NEW_DM libdm/mm/pool-fast.c
Date: 20 Oct 2011 13:39:58 -0000 [thread overview]
Message-ID: <20111020133958.456.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: zkabelac at sourceware.org 2011-10-20 13:39:57
Modified files:
. : WHATS_NEW_DM
libdm/mm : pool-fast.c
Log message:
Mark chunk memory for free as defined again for valgrind
When DEBUG_MEM is used, the memory is trashed with extra pattern before real
free() is called, and as this memory was marked as non accessible when used with
valgrind, make it again usable.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW_DM.diff?cvsroot=lvm2&r1=1.515&r2=1.516
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/libdm/mm/pool-fast.c.diff?cvsroot=lvm2&r1=1.14&r2=1.15
--- LVM2/WHATS_NEW_DM 2011/10/20 13:36:13 1.515
+++ LVM2/WHATS_NEW_DM 2011/10/20 13:39:57 1.516
@@ -1,5 +1,6 @@
Version 1.02.68 -
==================================
+ Fix valgrind error reports in free of pool chunks with DEBUG_MEM.
Aling size of structure chunk for fast pool allocator to 8 bytes.
Simplify some pointer operations in dm_free_aux() debug code.
Remove unused dbg_malloc.h file from source tree.
--- LVM2/libdm/mm/pool-fast.c 2011/08/11 17:29:05 1.14
+++ LVM2/libdm/mm/pool-fast.c 2011/10/20 13:39:57 1.15
@@ -300,6 +300,12 @@
static void _free_chunk(struct chunk *c)
{
+#ifdef VALGRIND_POOL
+# ifdef DEBUG_MEM
+ if (c)
+ VALGRIND_MAKE_MEM_UNDEFINED(c + 1, c->end - (char *) (c + 1));
+# endif
+#endif
dm_free(c);
}
next reply other threads:[~2011-10-20 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 13:39 zkabelac [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-10-20 14:43 LVM2 ./WHATS_NEW_DM libdm/mm/pool-fast.c zkabelac
2011-10-23 15:38 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=20111020133958.456.qmail@sourceware.org \
--to=zkabelac@sourceware.org \
--cc=lvm-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.