linux-kernel - [GIT PULL] Kmemleak fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Fri, 03 Jul 2009 23:02:30 +0100
From:	Catalin Marinas <catalin.marinas@....com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: [GIT PULL] Kmemleak fixes

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/