From: Catalin Marinas <catalin.marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Kmemleak fixes
Date: Tue, 30 Jun 2009 16:37:01 +0100 [thread overview]
Message-ID: <1246376222.22578.131.camel@pc1117.cambridge.arm.com> (raw)
Hi Linus,
Could you please merge the kmemleak branch detailed below? It contains
fixes aimed at reducing the false positives and the syslog backtraces.
Thanks.
The following changes since commit 28d0325ce6e0a52f53d8af687e6427fee59004d3:
Linus Torvalds (1):
Linux 2.6.31-rc1
are available in the git repository at:
git://linux-arm.org/linux-2.6.git kmemleak
Catalin Marinas (8):
kmemleak: Allow the early log buffer to be configurable.
kmemleak: Enable task stacks scanning by default
kmemleak: Simplify the reports logged by the scanning thread
kmemleak: Do not trigger a scan when reading the debug/kmemleak file
kmemleak: Slightly change the policy on newly allocated objects
kmemleak: Do not report new leaked objects if the scanning was stopped
kmemleak: Do not warn if an unknown object is freed
kmemleak: Inform kmemleak about pid_hash
Documentation/kmemleak.txt | 23 ++++--
kernel/pid.c | 7 ++
lib/Kconfig.debug | 12 +++
mm/kmemleak.c | 166 ++++++++++++++++++-------------------------
4 files changed, 105 insertions(+), 103 deletions(-)
--
Catalin
next reply other threads:[~2009-06-30 15:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 15:37 Catalin Marinas [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-28 15:27 [GIT PULL] kmemleak fixes Catalin Marinas
2009-07-09 17:29 [GIT PULL] Kmemleak fixes Catalin Marinas
2009-07-03 22:02 Catalin Marinas
2009-06-23 15:01 Catalin Marinas
2009-06-17 17:35 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=1246376222.22578.131.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®