From: Ingo Molnar <mingo@elte.hu>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, paulmck@us.ibm.com,
a.p.zijlstra@chello.nl, Vegard Nossum <vegard.nossum@gmail.com>
Subject: Re: [git pull] RCU updates for v2.6.27
Date: Wed, 16 Jul 2008 01:06:46 +0200 [thread overview]
Message-ID: <20080715230646.GB31249@elte.hu> (raw)
In-Reply-To: <84144f020807151401s2e37b892q2df007c9e1e3464a@mail.gmail.com>
* Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> There are now three commits in your tree that fix a real bug reported
> by kmemcheck: 8410565f540db87ca938f56f92780d251e4f157d ("ACPICA: Fix
> for access to deleted object <regression>"),
> adeed48090fc370afa0db8d007748ee72a40b578 ("rc80211_pid: Fix fast_start
> parameter handling"), and 62f75532b583c03840f31e40386ce2df73be9ca0
> ("slub: Initialize per-cpu stats").
there's a fourth one that i found via kmemcheck and which got fixed by
Jens but the commit log doesnt mention that it was found via kmemcheck:
| commit 63a7138671c50a6f2c27bbd1a308dc75967062a3
| Author: Jens Axboe <jens.axboe@oracle.com>
| Date: Fri Feb 8 12:41:03 2008 +0100
|
| block: fixup rq_init() a bit
> So I think it has been helpful and that the infrastructure it adds is
> valuable for future debugging aids.
even if it was not finding any bugs it would be useful to us - it has
already cleaned up a few dusty aspects of x86 code. (it might be similar
for SLUB)
Oh, and kmemcheck got Vegard to hack Linux ;-)
Ingo
prev parent reply other threads:[~2008-07-15 23:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 15:20 [git pull] RCU updates for v2.6.27 Ingo Molnar
2008-07-15 17:38 ` Linus Torvalds
2008-07-15 19:15 ` Ingo Molnar
2008-07-15 20:14 ` Vegard Nossum
2008-07-16 17:00 ` Andi Kleen
2008-07-16 17:18 ` Vegard Nossum
2008-07-15 20:15 ` Andrew Morton
2008-07-15 20:29 ` Linus Torvalds
2008-07-15 21:01 ` Pekka Enberg
2008-07-15 23:06 ` Ingo Molnar [this message]
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=20080715230646.GB31249@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@us.ibm.com \
--cc=penberg@cs.helsinki.fi \
--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