From: Nick Bowler <nbowler@elliptictech.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] kmemleak: Report previously found leaks even after an error
Date: Tue, 4 Oct 2011 13:45:48 -0400 [thread overview]
Message-ID: <20111004174548.GA16209@elliptictech.com> (raw)
In-Reply-To: <20110929110239.10660.95998.stgit@e102109-lin.cambridge.arm.com>
On 2011-09-29 12:02 +0100, Catalin Marinas wrote:
> If an error fatal to kmemleak (like memory allocation failure) happens,
> kmemleak disables itself but it also removes the access to any
> previously found memory leaks. This patch allows read-only access to the
> kmemleak debugfs interface but disables any other action.
>
> Repored-by: Nick Bowler <nbowler@elliptictech.com>
Reported-by: ...
> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Cool, I'll try this out. Kmemleak rarely stays alive for more than a
few days on my desktop before shutting itself down due to an allocation
failure, so this should be really handy.
Cheers,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
next prev parent reply other threads:[~2011-10-04 17:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 11:02 [PATCH 0/4] Kmemleak patches for -next Catalin Marinas
2011-09-29 11:02 ` [PATCH 1/4] kmemleak: Show where early_log issues come from Catalin Marinas
2011-09-29 11:02 ` [PATCH 2/4] kmemleak: Handle percpu memory allocation Catalin Marinas
2011-09-29 11:56 ` Eric Dumazet
2011-09-29 17:17 ` Catalin Marinas
2011-09-29 17:57 ` Christoph Lameter
2011-09-29 19:28 ` Tejun Heo
2011-09-30 8:37 ` Catalin Marinas
2011-10-03 15:21 ` Catalin Marinas
2011-10-03 16:14 ` Christoph Lameter
2011-10-04 7:59 ` Tejun Heo
2011-10-04 9:04 ` Catalin Marinas
2011-10-04 9:13 ` Tejun Heo
2011-10-04 9:26 ` Catalin Marinas
2011-10-04 16:59 ` Tejun Heo
2011-10-04 17:06 ` Catalin Marinas
2011-09-29 11:02 ` [PATCH 3/4] kmemleak: When the early log buffer is exceeded, report the actual number Catalin Marinas
2011-09-29 11:02 ` [PATCH 4/4] kmemleak: Report previously found leaks even after an error Catalin Marinas
2011-10-04 17:45 ` Nick Bowler [this message]
2011-10-04 20:50 ` Catalin Marinas
2011-10-04 21:14 ` Nick Bowler
2011-10-24 18:57 ` Nick Bowler
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=20111004174548.GA16209@elliptictech.com \
--to=nbowler@elliptictech.com \
--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;
as well as URLs for NNTP newsgroup(s).