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: Thu, 09 Jul 2009 18:29:20 +0100 [thread overview]
Message-ID: <1247160560.11409.96.camel@pc1117.cambridge.arm.com> (raw)
Hi Linus,
Would you please consider merging the kmemleak branch?
It contains several fixes to bugs raised recently and also reduces the
number of false positives to nearly 0 (actually making the tool usable -
one of the slub kmalloc calls for large blocks was completely missed and
bootmem allocations would need to be tracked as well since many of them
contain valid pointers).
Thanks.
The following changes since commit 34f25476ace556263784ea2f8173e22b25557a13:
Linus Torvalds (1):
Merge branch 'fixes' of git://git.kernel.org/.../davej/cpufreq
are available in the git repository at:
git://linux-arm.org/linux-2.6 kmemleak
Catalin Marinas (9):
kmemleak: Renice the scanning thread to +10
kmemleak: Add more cond_resched() calls in the scanning thread
kmemleak: Remove the reported leaks number limitation
kmemleak: Do not acquire scan_mutex in kmemleak_open()
kmemleak: Scan objects allocated during a scanning episode
kmemleak: Trace the kmalloc_large* functions in slub
kmemleak: Allow partial freeing of memory blocks
kmemleak: Add callbacks to the bootmem allocator
kmemleak: Remove alloc_bootmem annotations introduced in the past
include/linux/kmemleak.h | 4 +
include/linux/slub_def.h | 2 +
kernel/pid.c | 7 --
mm/bootmem.c | 6 +
mm/kmemleak.c | 236 ++++++++++++++++++++++++++++++++--------------
mm/page_alloc.c | 14 +--
mm/slub.c | 10 +-
7 files changed, 185 insertions(+), 94 deletions(-)
--
Catalin
next reply other threads:[~2009-07-09 17:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 17:29 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-03 22:02 [GIT PULL] Kmemleak fixes Catalin Marinas
2009-06-30 15:37 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=1247160560.11409.96.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®