linux-kernel - [PATCH 0/5] mm, slob: Tracing accuracy improvement

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:	Wed, 5 Sep 2012 19:50:47 -0300
From:	Ezequiel Garcia <elezegarcia@...il.com>
To:	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	Pekka Enberg <penberg@...nel.org>,
	Christoph Lameter <cl@...ux.com>,
	Glauber Costa <glommer@...allels.com>,
	Tim Bird <tim.bird@...sony.com>,
	Steven Rostedt <rostedt@...dmis.org>
Subject: [PATCH 0/5] mm, slob: Tracing accuracy improvement

Hi everyone,

This small patchset improves mm tracing accuracy, particularly on the
slob allocator.
Feedback, comments, suggestions are very welcome.

This work is part of CELF Workgroup Project:
"Kernel_dynamic_memory_allocation_tracking_and_reduction" [1]

Ezequiel Garcia (5):
 mm, slob: Trace allocation failures consistently
 mm, slob: Use only 'ret' variable for both slob object and returned pointer
 mm, util: Do strndup_user allocation directly, instead of through memdup_user
 mm, slob: Add support for kmalloc_track_caller()
 mm, slab: Remove silly function slab_buffer_size()

 include/linux/slab.h |    6 +++-
 mm/slab.c            |   12 +--------
 mm/slob.c            |   62 +++++++++++++++++++++++++++++++++++--------------
 mm/util.c            |   15 +++++++++--
 4 files changed, 62 insertions(+), 33 deletions(-)

Thanks!
Ezequiel.

[1] http://elinux.org/Kernel_dynamic_memory_allocation_tracking_and_reduction
--
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/