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_DM libdm/mm/pool-fast.c Date: Sun, 23 Oct 2011 15:38:00 -0000 [thread overview] Message-ID: <20111023153803.22574.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: zkabelac@sourceware.org 2011-10-23 15:38:03 Modified files: . : WHATS_NEW_DM libdm/mm : pool-fast.c Log message: Fix usage of DEBUG_ENFORCE_POOL_LOCKING with DEBUG_MEM Since DEBUG_MEM is storing own extra structure within returned memory chunk, glibc free must be used directly for posix_memaling() allocated block. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW_DM.diff?cvsroot=lvm2&r1=1.517&r2=1.518 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/libdm/mm/pool-fast.c.diff?cvsroot=lvm2&r1=1.16&r2=1.17 --- LVM2/WHATS_NEW_DM 2011/10/20 14:43:33 1.517 +++ LVM2/WHATS_NEW_DM 2011/10/23 15:38:02 1.518 @@ -1,5 +1,6 @@ Version 1.02.68 - ================================== + Fix compile-time pool memory locking with DEBUG_MEM. Fix valgrind error reports in free of pool chunks with DEBUG_MEM. Align size of structure chunk for fast pool allocator to 8 bytes. Simplify some pointer operations in dm_free_aux() debug code. --- LVM2/libdm/mm/pool-fast.c 2011/10/20 14:43:33 1.16 +++ LVM2/libdm/mm/pool-fast.c 2011/10/23 15:38:03 1.17 @@ -306,7 +306,12 @@ VALGRIND_MAKE_MEM_UNDEFINED(c + 1, c->end - (char *) (c + 1)); # endif #endif +#ifdef DEBUG_ENFORCE_POOL_LOCKING + /* since DEBUG_MEM is using own memory list */ + free(c); /* for posix_memalign() */ +#else dm_free(c); +#endif }
next reply other threads:[~2011-10-23 15:38 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-23 15:38 zkabelac [this message] -- strict thread matches above, loose matches on Subject: below -- 2011-10-20 14:43 zkabelac 2011-10-20 13:39 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=20111023153803.22574.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: linkBe 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).