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]

Message-Id: <1246376222.22578.131.camel@pc1117.cambridge.arm.com>
Date:	Tue, 30 Jun 2009 16:37:01 +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 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

--
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/