linux-kernel - [PATCH 0/8] Kmemleak patches for 2.6.32

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>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090724161026.5752.52503.stgit@pc1117.cambridge.arm.com>
Date:	Fri, 24 Jul 2009 17:12:01 +0100
From:	Catalin Marinas <catalin.marinas@....com>
To:	linux-kernel@...r.kernel.org
Subject: [PATCH 0/8] Kmemleak patches for 2.6.32

Hi,

These are kmemleak related patches I plan to submit for mainline
inclusion during the upcoming merging window. I'll push them to the
linux-next tree once any comments received are implemented.

Thanks.


Catalin Marinas (7):
      kmemleak: Dump object information on request
      kmemleak: Allow rescheduling during an object scanning
      kmemleak: Mark the early log buffer as __initdata
      kmemleak: Save the stack trace for early allocations
      kmemleak: Do not report alloc_bootmem blocks as leaks
      kmemleak: Inform kmemleak about kernel stack allocation
      kmemleak: Always scan the task stacks

Sergey Senozhatsky (1):
      kmemleak: Printing of the objects hex dump


 Documentation/kmemleak.txt         |   12 +-
 arch/x86/include/asm/thread_info.h |    7 +
 arch/x86/kernel/process.c          |    1 
 include/linux/kmemleak.h           |   18 ++-
 kernel/fork.c                      |    7 +
 mm/bootmem.c                       |    6 +
 mm/kmemleak.c                      |  195 +++++++++++++++++++++++++++---------
 7 files changed, 178 insertions(+), 68 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/