From: Andrew Morton <akpm@osdl.org>
To: Zach Brown <zach.brown@oracle.com>
Cc: rdunlap@xenotime.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kmap tracking
Date: Mon, 22 May 2006 10:39:15 -0700 [thread overview]
Message-ID: <20060522103915.53e03867.akpm@osdl.org> (raw)
In-Reply-To: <4471EA2C.4010401@oracle.com>
Zach Brown <zach.brown@oracle.com> wrote:
>
> Randy.Dunlap wrote:
> > From: Randy Dunlap <rdunlap@xenotime.net>
> >
> > Track kmap/kunmap call history, storing caller function address,
> > action, and time (jiffies), if CONFIG_DEBUG_KMAP is enabled.
> > Based on a patch to 2.4.21 by Zach Brown that was used successfully
> > at Oracle to track down some kmap/kunmap problems.
>
> Thanks for bringing this to 2.6.. sorry for the lag in reviewing.
I was scratching my head over this patch trying to think of any bug in
recent years which it would have detected. I failed.
So... what's the motivator here?
next prev parent reply other threads:[~2006-05-22 17:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 22:53 Randy.Dunlap
2006-05-22 16:43 ` Zach Brown
2006-05-22 17:39 ` Andrew Morton [this message]
2006-05-22 17:58 ` Zach Brown
2006-05-22 18:11 ` Randy.Dunlap
2006-05-23 18:42 ` Randy.Dunlap
2006-05-24 1:59 ` Randy.Dunlap
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=20060522103915.53e03867.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=zach.brown@oracle.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®