From: Jeff Dike <jdike@karaya.com>
To: John Reiser <jreiser@BitWagon.com>
Cc: linux-kernel@vger.kernel.org,
Jeremy Fitzhardinge <jeremy@goop.org>,
Julian Seward <jseward@acm.org>
Subject: Re: Valgrind meets UML
Date: Fri, 20 Dec 2002 17:58:18 -0500 [thread overview]
Message-ID: <200212202258.RAA03444@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Fri, 20 Dec 2002 07:26:39 PST." <3E0336AF.6060607@BitWagon.com>
jreiser@BitWagon.com said:
> Implementors of allocators can have bugs in the valgrind declarations
> they add. An "independent" check based on documented
> externally-visible behavior can help.
The problem is that valgrind is going to look under the covers of the kernel
allocators and see the externally-visible requirements being violated.
Either you implement a globally correct description, which includes the
externally visible description as a subset, or you somehow tell valgrind not
to complain about stuff inside the allocator.
The second sounds complicated, and anyway hides bugs in the allocator.
> Nested allocators (inner allocator grabs a large region, outer
> allocator performs sub-allocations of small pieces from the large
> region) can be troublesome.
And are another reason for implementing a globally correct description.
Jeff
next prev parent reply other threads:[~2002-12-20 22:46 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 [this message]
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
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=200212202258.RAA03444@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