From: Kevin Winchester <kjwinchester@gmail.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: kmemleak reports
Date: Tue, 14 Jul 2009 20:28:10 -0300 [thread overview]
Message-ID: <4A5D148A.5090405@gmail.com> (raw)
Hi Catalin,
I have noticed a few kmemleak reports being sent to LKML in the last few days, and I could chime in with mine, if you wish:
kmemleak: 97 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
The entries are for X, ntpdate, scsi_scan_2, softirq, swapper, in case there's anything surprising in there.
However, I was thinking that you might soon start getting too many reports to process. I wonder if there might be some way that you could have a similar facility to kerneloops that would automatically register leak reports to a website where they could be organized and ranked by number of occurrences. Are the individual leaks reported in such at way that would allow them to be grouped like that?
If a kerneloops-style setup is not desirable/feasible, would you be able to send me a walkthrough for how you go about tracking down one of these leaks? Then I might be able to help out by investigating a few of my own.
Thanks,
--
Kevin Winchester
next reply other threads:[~2009-07-14 23:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 23:28 Kevin Winchester [this message]
2009-07-15 10:46 ` kmemleak reports Catalin Marinas
2009-07-16 9:11 ` Catalin Marinas
2009-07-16 16:13 ` Catalin Marinas
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=4A5D148A.5090405@gmail.com \
--to=kjwinchester@gmail.com \
--cc=arjan@infradead.org \
--cc=catalin.marinas@arm.com \
--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