Re: [PATCH 2.6.18-rc4 00/10] Kernel memory leak detector 0.9

["Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>]

Hi Catalin,

On 17/08/06, Catalin Marinas <catalin.marinas@gmail.com> wrote:
> On 17/08/06, Catalin Marinas <catalin.marinas@gmail.com> wrote:
> > I'm not sure it's a good idea, it might have other implications in
> > slab.c. I better fix kmemleak (I think currently you could get a
> > deadlock only on SMP).
>
> I attach a patch for kmemleak-0.9 which seems to work for me. It has a
> new locking mechanism in that memory allocations are performed without
> memleak_lock held. Let me know if you still get errors (I haven't
> fully tested it yet).

Something doesn't work. It appears while udev start.

[<c0106cdc>] show_trace+0xd/0xf
[<c0106dae>] dump_stack+0x17/0x19
[<c016e9a0>] __kmalloc+0xf6/0x10a
[<c019a4bf>] load_elf_binary+0x5b/0xb46
[<c017d77a>] search_binary_handler+0xfc/0x2d4
[<c017daa5>] do_execve+0x153/0x1f0
[<c0104d5f>] sys_execve+0x29/0x7a
[<c0105f11>] sysenter_past_esp+0x5b/0x79
kmemleak: pointer 0xf5a39ae0:
trace:
c016e767: <kmemleak_cache_alloc>
c0127274: <dup_mm>
c0127427: <copy_mm>
c0128227: <copy_process>
c012893: <do_fork>
c0104d19: <sys_clone>

Kernel panic - not syncing: kmemleak: resizing pointer by alias 0xf5ad4a04

BUG: warning at
/usr/src/linux-work8/arch/i386/kernel/smp.c:547/smp_call_function()
[<c0106cdc>] show_trace+0xd/0xf
[<c0106dae>] dump_stack+0x17/0x19
[<c0116ac4>] smp_call_function+0x52/0xf9
[<c0116bad>] smp_send_stop+0x16/0x20
[<c0170c35>] panic+0x50/0xdf
[<c016e9a0>] __kmalloc+0xf6/0x10a
[<c019a4bf>] load_elf_binary+0x5b/0xb46
[<c017d77a>] search_binary_handler+0xfc/0x2d4
[<c017daa5>] do_execve+0x153/0x1f0
[<c0104d5f>] sys_execve+0x29/0x7a
[<c0105f11>] sysenter_past_esp+0x5b/0x79

http://www.stardust.webpages.pl/files/o_bugs/kmemleak-0.9/kml-config2

> Thanks.
>
> --
> Catalin

Regards,
Michal

--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)
-
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/