Alexander Nyberg wrote:
My fault, I introduced a debugging patch (i think i cc'ed you on it) which used __builtin_return_address([12]) to save traces of who the caller of an object is.
Ups. I still have your original mail in my inbox.The correct way is check the whole stack and store all pointers that are in kernel_text_address(). See store_stack_info() in mm/slab.c.
-- Manfred - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [SLAB] __builtin_return_address use without FRAME_POINTER causes boot failure
- From: Jörn Engel <joern@wohnheim.fh-wedel.de>
- Re: [SLAB] __builtin_return_address use without FRAME_POINTER causes boot failure
- References:
- [SLAB] __builtin_return_address use without FRAME_POINTER causes boot failure
- From: Christoph Lameter <christoph@lameter.com>
- Re: [SLAB] __builtin_return_address use without FRAME_POINTER causes boot failure
- From: Manfred Spraul <manfred@colorfullife.com>
- Re: [SLAB] __builtin_return_address use without FRAME_POINTER causes boot failure
- From: Alexander Nyberg <alexn@telia.com>
- [SLAB] __builtin_return_address use without FRAME_POINTER causes boot failure
- Prev by Date: Re: Patch of a new driver for kernel 2.4.x that need review
- Next by Date: Re: [PATCH 2/4] Task notifier: Implement todo list in task_struct
- Previous by thread: Re: [SLAB] __builtin_return_address use without FRAME_POINTER causes boot failure
- Next by thread: Re: [SLAB] __builtin_return_address use without FRAME_POINTER causes boot failure
- Index(es):
