linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Jianguo Wu <wujianguo@huawei.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"rob@landley.net" <rob@landley.net>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Li Zefan <lizefan@huawei.com>, Wang Nan <wangnan0@huawei.com>
Subject: Re: [PATCH] mm/kmemleak: add support for re-enable kmemleak at runtime
Date: Fri, 17 Jan 2014 12:04:36 +0000	[thread overview]
Message-ID: <20140117120436.GC28895@arm.com> (raw)
In-Reply-To: <52D8FA72.8080100@huawei.com>

On Fri, Jan 17, 2014 at 09:40:02AM +0000, Jianguo Wu wrote:
> Now disabling kmemleak is an irreversible operation, but sometimes
> we may need to re-enable kmemleak at runtime. So add a knob to enable
> kmemleak at runtime:
> echo on > /sys/kernel/debug/kmemleak

It is irreversible for very good reason: once it missed the initial
memory allocations, there is no way for kmemleak to build the object
reference graph and you'll get lots of false positives, pretty much
making it unusable.

-- 
Catalin

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2014-01-17 12:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17  9:40 Jianguo Wu
2014-01-17 12:04 ` Catalin Marinas [this message]
2014-01-18  8:41   ` Jianguo Wu
2014-01-18 10:45     ` 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=20140117120436.GC28895@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lizefan@huawei.com \
    --cc=rob@landley.net \
    --cc=wangnan0@huawei.com \
    --cc=wujianguo@huawei.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