From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] kmemcheck for mainline
Date: Fri, 12 Jun 2009 16:57:04 +0300 [thread overview]
Message-ID: <84144f020906120657j31fb3e82t2da251d31db6ba92@mail.gmail.com> (raw)
In-Reply-To: <20090612132443.GA24002@damson.ad.medicalresearch.no>
Hi Linus,
On Fri, Jun 12, 2009 at 4:31 PM, Vegard Nossum<vegard.nossum@gmail.com> wrote:
> Please consider pulling the kmemcheck tree;
>
> kmemcheck is a feature which can (at run-time) detect some uses of
> uninitialized memory within the kernel, similarly to what Valgrind's memcheck
> does for userspace programs. We also have the ability to find use-after-free
> errors and leaks of uninitialized data to userspace, both with a false-
> positive rate of zero.
>
> kmemcheck is self-contained in the sense that when CONFIG_KMEMCHECK=n, it has
> no effect on the compiled kernel whatsoever. Our code has lived in the -tip
> tree and been in -next for over a year, and has the acks of x86 and slab
> maintainers (Ingo and Pekka). Inclusion in mainline would lower the threshold
> for building and running kmemcheck-enabled kernels, which would also
> hopefully increase testing coverage of the rest of the kernel code.
I hope I didn't burn all my karma for this merge window with the slab
early boot patches but:
Acked-by: Pekka Enberg <penberg@cs.helsinki.fi>
for this pull request.
Pekka
next prev parent reply other threads:[~2009-06-12 13:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 13:31 Vegard Nossum
2009-06-12 13:57 ` Pekka Enberg [this message]
2009-06-12 14:00 ` Ingo Molnar
2009-06-12 16:38 ` Linus Torvalds
2009-06-12 16:41 ` Linus Torvalds
2009-06-12 16:45 ` Ingo Molnar
2009-06-15 14:59 ` Vegard Nossum
2009-06-16 16:21 ` Pekka Enberg
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=84144f020906120657j31fb3e82t2da251d31db6ba92@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
--cc=vegard.nossum@gmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®