mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Kevin Winchester <kjwinchester@gmail.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: kmemleak reports
Date: Thu, 16 Jul 2009 10:11:45 +0100	[thread overview]
Message-ID: <1247735505.24965.15.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <4A5D148A.5090405@gmail.com>

On Tue, 2009-07-14 at 20:28 -0300, Kevin Winchester wrote:
> 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?

BTW, a step towards reducing the number of reports on the list is to
maintain a tree based on the mainline which gathers various fixes posted
by people. It is up to the maintainers to push them upstream but, in the
meantime, people could try this tree and avoid reporting the same
issues.

I'll try to set this up, ideally on kernel.org for wider visibility (if
I manage to get an account, otherwise on linux-arm.org/git where I
usually keep my trees).

-- 
Catalin


  parent reply	other threads:[~2009-07-16  9:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14 23:28 Kevin Winchester
2009-07-15 10:46 ` Catalin Marinas
2009-07-16  9:11 ` Catalin Marinas [this message]
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=1247735505.24965.15.camel@pc1117.cambridge.arm.com \
    --to=catalin.marinas@arm.com \
    --cc=arjan@infradead.org \
    --cc=kjwinchester@gmail.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

all inboxes | Powered by JetHome®