qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Lucas Meneghel Rodrigues <lmr@redhat.com>,
	qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] tests: set MALLOC_PERTURB_ to expose memory bugs
Date: Tue, 21 May 2013 17:17:15 +0200	[thread overview]
Message-ID: <20130521151715.GA8903@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <519B6EE7.30207@redhat.com>

On Tue, May 21, 2013 at 06:56:07AM -0600, Eric Blake wrote:
> On 05/21/2013 06:43 AM, Stefan Hajnoczi wrote:
> > glibc wipes malloc(3) memory when the MALLOC_PERTURB_ environment
> > variable is set.  The value of the environment variable determines the
> > bit pattern used to wipe memory.  For more information, see
> > http://udrepper.livejournal.com/11429.html.
> > 
> > Set MALLOC_PERTURB_ for gtester and qemu-iotests.  Note we pick a random
> > value from 1 to 255 to expose more bugs.  If you need to reproduce a
> > crash use 'show environment' in gdb to extract the MALLOC_PERTURB_
> > value from a core dump.
> > 
> > Both make check and qemu-iotests pass with MALLOC_PERTURB_ enabled.
> > 
> > Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> > ---
> >  tests/Makefile           | 5 ++++-
> >  tests/qemu-iotests/check | 3 ++-
> >  2 files changed, 6 insertions(+), 2 deletions(-)
> > 
> > diff --git a/tests/Makefile b/tests/Makefile
> > index a307d5a..24880c6 100644
> > --- a/tests/Makefile
> > +++ b/tests/Makefile
> > @@ -171,6 +171,7 @@ GCOV_OPTIONS = -n $(if $(V),-f,)
> >  $(patsubst %, check-qtest-%, $(QTEST_TARGETS)): check-qtest-%: $(check-qtest-y)
> >  	$(if $(CONFIG_GCOV),@rm -f *.gcda */*.gcda */*/*.gcda */*/*/*.gcda,)
> >  	$(call quiet-command,QTEST_QEMU_BINARY=$*-softmmu/qemu-system-$* \
> > +		MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(($RANDOM % 255 + 1))} \
> 
> This is a Makefile; don't you need to use $$ instead of $ (three instances)?
> 
> $RANDOM is a bash-ism.  If make is run with SHELL as /bin/sh on a
> platform where dash is the primary shell, it will fail:
> 
> $ dash -c 'echo $(($RANDOM % 255))'
> dash: 1: arithmetic expression: expecting primary: " % 255"
> 
> HOWEVER: you can exploit the fact that inside $(()), you don't need $ to
> use the value of a defined variable, and also the fact that unless set
> -u is in effect, an undefined variable name silently evaluates as 0:
> 
> $ dash -c 'echo $((RANDOM % 255))'
> 0
> 
> then you could write the shell code:
> 
> 	MALLOC_PERTURB_=${MALLOC_PERTURB_:-$((RANDOM % 255 + 1))}
> 
> or the Makefile code:
> 
> 	MALLOC_PERTURB_=$${MALLOC_PERTURB_:-$$((RANDOM % 255 + 1))}
> 
> and things will at least work on /bin/sh as dash (even though there will
> be no randomness and you are always testing with 1 in that case).

Silly me.  I did test it but it silently "worked".

Will resend.

Stefan

  reply	other threads:[~2013-05-21 15:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-21 12:43 [Qemu-devel] [PATCH v2] tests: set MALLOC_PERTURB_ to expose memory bugs Stefan Hajnoczi
2013-05-21 12:56 ` Eric Blake
2013-05-21 15:17   ` Stefan Hajnoczi [this message]
2013-05-21 15:58     ` Eric Blake

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=20130521151715.GA8903@stefanha-thinkpad.redhat.com \
    --to=stefanha@redhat.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=lmr@redhat.com \
    --cc=qemu-devel@nongnu.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 NNTP newsgroup(s).