mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 patches
Date: Fri, 04 Dec 2009 10:02:54 +0000	[thread overview]
Message-ID: <1259920974.12495.11.camel@pc1117.cambridge.arm.com> (raw)

Hi Linus,

Could you please merge the kmemleak branch below? It contains some
improvements to kmemleak (including reduced rate of false positives).
Thanks.

The following changes since commit 012abeea669ea49636cf952d13298bb68654146a:
  Linus Torvalds (1):
        Linux 2.6.32-rc5

are available in the git repository at:

  git://linux-arm.org/linux-2.6.git kmemleak

Catalin Marinas (6):
      kmemleak: Do not use off-slab management with SLAB_NOLEAKTRACE
      kmemleak: Simplify the kmemleak_scan_area() function prototype
      kmemleak: Scan the _ftrace_events section in modules
      kmemleak: Release the object lock before calling put_object()
      kmemleak: Show the age of an unreferenced object
      kmemleak: Reduce the false positives by checking for modified objects

Randy Dunlap (1):
      kmemleak: fix kconfig for crc32 build error

 include/linux/kmemleak.h |    6 +-
 kernel/module.c          |   13 ++-
 lib/Kconfig.debug        |    1 +
 mm/kmemleak.c            |  188 +++++++++++++++++++++++++---------------------
 mm/slab.c                |   10 ++-
 5 files changed, 118 insertions(+), 100 deletions(-)

-- 
Catalin


             reply	other threads:[~2009-12-04 10:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-04 10:02 Catalin Marinas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-10-25 15:45 Catalin Marinas
2009-12-11 15:57 Catalin Marinas
2009-09-11 12:08 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=1259920974.12495.11.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®