linux-kernel - Re: [PATCH V2] slab: fix caller tracking on !CONFIG_DEBUG_SLAB && CONFIG

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

Date:	Sun, 04 Jul 2010 19:50:56 +0300
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	David Rientjes <rientjes@...gle.com>
CC:	Xiaotian Feng <dfeng@...hat.com>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org,
	Christoph Lameter <cl@...ux-foundation.org>,
	Matt Mackall <mpm@...enic.com>,
	Vegard Nossum <vegard.nossum@...il.com>,
	Dmitry Monakhov <dmonakhov@...nvz.org>,
	Catalin Marinas <catalin.marinas@....com>
Subject: Re: [PATCH V2] slab: fix caller tracking on !CONFIG_DEBUG_SLAB &&
 CONFIG_TRACING

David Rientjes wrote:
> On Wed, 30 Jun 2010, Xiaotian Feng wrote:
> 
>> In slab, all __xxx_track_caller is defined on CONFIG_DEBUG_SLAB || CONFIG_TRACING,
>> thus caller tracking function should be worked for CONFIG_TRACING. But if
>> CONFIG_DEBUG_SLAB is not set, include/linux/slab.h will define xxx_track_caller to
>> __xxx() without consideration of CONFIG_TRACING. This will break the caller tracking
>> behaviour then.
>>
>> Signed-off-by: Xiaotian Feng <dfeng@...hat.com>
>> Cc: Christoph Lameter <cl@...ux-foundation.org>
>> Cc: Pekka Enberg <penberg@...helsinki.fi>
>> Cc: Matt Mackall <mpm@...enic.com>
>> Cc: Vegard Nossum <vegard.nossum@...il.com>
>> Cc: Dmitry Monakhov <dmonakhov@...nvz.org>
>> Cc: Catalin Marinas <catalin.marinas@....com>
>> Cc: David Rientjes <rientjes@...gle.com>
> 
> Acked-by: David Rientjes <rientjes@...gle.com>

Applied, thanks!
--
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/