mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Alexander Monakov <amonakov@ispras.ru>
To: musl@lists.openwall.com
Subject: [RFC PATCH] Allow annotating calloc for Valgrind
Date: Fri, 30 Jun 2017 01:56:14 +0300	[thread overview]
Message-ID: <20170629225614.19061-1-amonakov@ispras.ru> (raw)

With mal0_clear entered only for larger-than-one-page allocations, a
few additional nops and stack accesses don't matter.

This only needs Valgrind headers to build, Valgrind itself doesn't need to be
built/installed.  However, valgrind.h unconditionally includes stdarg.h.

Untested.
---
 configure           | 11 +++++++++++
 src/malloc/malloc.c |  4 ++++
 2 files changed, 15 insertions(+)

diff --git a/configure b/configure
index c2db298c..7e78094f 100755
--- a/configure
+++ b/configure
@@ -30,6 +30,7 @@ System types:
 Optional features:
   --enable-optimize=...   optimize listed components for speed over size [auto]
   --enable-debug          build with debugging information [disabled]
+  --enable-valgrind       add Valgrind annotations [disabled]
   --enable-warnings       build with recommended warnings flags [disabled]
   --enable-visibility     use global visibility options to optimize PIC [auto]
   --enable-wrapper=...    build given musl toolchain wrapper [auto]
@@ -134,6 +135,7 @@ build=
 target=
 optimize=auto
 debug=no
+valgrind=no
 warnings=no
 visibility=auto
 shared=auto
@@ -161,6 +163,8 @@ case "$arg" in
 --disable-optimize) optimize=no ;;
 --enable-debug|--enable-debug=yes) debug=yes ;;
 --disable-debug|--enable-debug=no) debug=no ;;
+--enable-valgrind|--enable-valgrind=yes) valgrind=yes ;;
+--disable-valgrind|--enable-valgrind=no) valgrind=no ;;
 --enable-warnings|--enable-warnings=yes) warnings=yes ;;
 --disable-warnings|--enable-warnings=no) warnings=no ;;
 --enable-visibility|--enable-visibility=yes) visibility=yes ;;
@@ -390,6 +394,13 @@ tryflag CFLAGS_MEMOPS -fno-tree-loop-distribute-patterns
 #
 test "$debug" = yes && CFLAGS_AUTO=-g
 
+if test x"$valgrind" = xyes  ; then
+CPPFLAGS="$CPPFLAGS -DVG_MEMCHECK_H='<memcheck.h>'"
+else
+CPPFLAGS="$CPPFLAGS -DVG_MEMCHECK_H='</dev/null>'"
+fi
+CPPFLAGS="${CPPFLAGS# }"
+
 #
 # Preprocess asm files to add extra debugging information if debug is
 # enabled, our assembler supports the needed directives, and the
diff --git a/src/malloc/malloc.c b/src/malloc/malloc.c
index b56fdaa2..d4c229bd 100644
--- a/src/malloc/malloc.c
+++ b/src/malloc/malloc.c
@@ -8,6 +8,7 @@
 #include "libc.h"
 #include "atomic.h"
 #include "pthread_impl.h"
+#include VG_MEMCHECK_H
 
 #if defined(__GNUC__) && defined(__PIC__)
 #define inline inline __attribute__((always_inline))
@@ -373,6 +374,9 @@ static size_t mal0_clear(char *p, size_t pagesz, size_t n)
 	typedef unsigned long long T;
 	char *pp = p + n;
 	size_t i = (uintptr_t)pp & (pagesz - 1);
+#ifdef VALGRIND_MAKE_MEM_DEFINED_IF_ADDRESSABLE
+	VALGRIND_MAKE_MEM_DEFINED_IF_ADDRESSABLE(p, n);
+#endif
 	for (;;) {
 		pp = memset(pp - i, 0, i);
 		if (pp - p < pagesz) return pp - p;
-- 
2.11.0



             reply	other threads:[~2017-06-29 22:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-29 22:56 Alexander Monakov [this message]
2017-06-29 23:20 ` Rich Felker
2017-06-29 23:42   ` Alexander Monakov
2017-06-29 23:56     ` Rich Felker
2017-07-02 13:55       ` Alexander Monakov
2017-07-02 14:35         ` Rich Felker
2017-07-02 16:16           ` Alexander Monakov
2017-07-02 16:31             ` Rich Felker

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=20170629225614.19061-1-amonakov@ispras.ru \
    --to=amonakov@ispras.ru \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).