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 fixes
Date: Fri, 03 Jul 2009 23:02:30 +0100	[thread overview]
Message-ID: <1246658550.13969.3.camel@pc1117.cambridge.arm.com> (raw)

Hi Linus,

Could you please pull the kmemleak branch? This is hopefully the last
set of kmemleak changes for 2.6.31 (there may be some false positive
annotations). It seems to be consistent on my x86 hardware now but with
a few leak reports which I need to look at.

Thanks.


The following changes since commit 7c5371c403abb29f01bc6cff6c5096abdf2dc524:
  Yinghai Lu (1):
        x86: add boundary check for 32bit res before expand e820 resource to alignment

are available in the git repository at:

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

Catalin Marinas (6):
      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

 include/linux/slub_def.h |    2 +
 mm/kmemleak.c            |  129 ++++++++++++++++++++++++++++------------------
 mm/slub.c                |   10 ++--
 3 files changed, 86 insertions(+), 55 deletions(-)

-- 
Catalin


             reply	other threads:[~2009-07-03 22:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-03 22:02 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-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=1246658550.13969.3.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®