public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@karaya.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: John Reiser <jreiser@BitWagon.com>,
	Linux Kernel List <linux-kernel@vger.kernel.org>,
	Julian Seward <jseward@acm.org>
Subject: Re: Valgrind meets UML
Date: Sat, 21 Dec 2002 11:05:25 -0500	[thread overview]
Message-ID: <200212211605.LAA01502@ccure.karaya.com> (raw)
In-Reply-To: Your message of "20 Dec 2002 23:32:21 PST." <1040455941.1841.123.camel@ixodes.goop.org>

jeremy@goop.org said:
> The main problem will be that newly allocated memory will still be
> considered initialized by its previous owner.  Also, if UML allocates
> memory using mmap, all memory will be considered to be initialized.

What I was doing was having kfree and free_pages set the freed object to
noaccess.  Presumably, that tells valgrind to consider the memory 
uninitialized.

Presumably, that will also cause errors from inside the allocator if it
touches that memory at all before it's allocated again.

				Jeff


  reply	other threads:[~2002-12-21 15:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-20  2:41 Valgrind meets UML Jeff Dike
2002-12-20 15:26 ` John Reiser
2002-12-20 22:58   ` Jeff Dike
2002-12-20 23:32     ` John Reiser
2002-12-21  2:49       ` Jeff Dike
2002-12-21  7:32         ` Jeremy Fitzhardinge
2002-12-21 16:05           ` Jeff Dike [this message]
2002-12-21 14:40 ` John Reiser
2002-12-21 16:07   ` Jeff Dike
2002-12-21 16:15     ` John Reiser
2002-12-21 18:57       ` Jeff Dike
2002-12-21 19:07   ` Jeremy Fitzhardinge

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=200212211605.LAA01502@ccure.karaya.com \
    --to=jdike@karaya.com \
    --cc=jeremy@goop.org \
    --cc=jreiser@BitWagon.com \
    --cc=jseward@acm.org \
    --cc=linux-kernel@vger.kernel.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