mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: "Catalin Marinas" <catalin.marinas@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.18-rc4 00/10] Kernel memory leak detector 0.9
Date: Fri, 18 Aug 2006 14:28:13 +0200	[thread overview]
Message-ID: <6bffcb0e0608180528ocadc36ck8868ae1a33342bb9@mail.gmail.com> (raw)
In-Reply-To: <b0943d9e0608171458l45b717bexbfb8fb2ba68228db@mail.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/)

  reply	other threads:[~2006-08-18 12:28 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-12 21:58 Catalin Marinas
2006-08-12 21:59 ` [PATCH 2.6.18-rc4 01/10] Base support for kmemleak Catalin Marinas
2006-08-12 22:00 ` [PATCH 2.6.18-rc4 02/10] Some documentation " Catalin Marinas
2006-08-12 22:00 ` [PATCH 2.6.18-rc4 03/10] Add the memory allocation/freeing hooks " Catalin Marinas
2006-08-12 22:00 ` [PATCH 2.6.18-rc4 04/10] Modules support " Catalin Marinas
2006-08-12 22:00 ` [PATCH 2.6.18-rc4 05/10] Add kmemleak support for i386 Catalin Marinas
2006-08-12 22:00 ` [PATCH 2.6.18-rc4 06/10] Add kmemleak support for ARM Catalin Marinas
2006-08-12 22:00 ` [PATCH 2.6.18-rc4 07/10] Remove some of the kmemleak false positives Catalin Marinas
2006-08-12 22:00 ` [PATCH 2.6.18-rc4 08/10] Keep the __init functions after initialization Catalin Marinas
2006-08-12 22:00 ` [PATCH 2.6.18-rc4 09/10] Simple testing for kmemleak Catalin Marinas
2006-08-12 22:01 ` [PATCH 2.6.18-rc4 10/10] Update the MAINTAINERS file " Catalin Marinas
2006-08-13 11:59 ` [PATCH 2.6.18-rc4 00/10] Kernel memory leak detector 0.9 Michal Piotrowski
2006-08-13 14:13   ` Catalin Marinas
2006-08-13 14:26     ` Michal Piotrowski
2006-08-17 13:02       ` Catalin Marinas
2006-08-17 14:45         ` Michal Piotrowski
2006-08-17 14:48           ` Michal Piotrowski
2006-08-17 15:04             ` Catalin Marinas
2006-08-17 15:01           ` Catalin Marinas
2006-08-17 21:58             ` Catalin Marinas
2006-08-18 12:28               ` Michal Piotrowski [this message]
2006-08-18 13:27                 ` Catalin Marinas
2006-08-18 13:55                   ` Michal Piotrowski
2006-08-18 14:15                     ` Michal Piotrowski
2006-08-18 15:46                       ` Catalin Marinas
2006-08-18 16:42                         ` Michal Piotrowski
2006-08-18 16:57                           ` Catalin Marinas
2006-08-18 21:38                             ` Michal Piotrowski
2006-08-18 21:47                               ` Catalin Marinas
2006-08-18 22:49                                 ` Michal Piotrowski
2006-08-19 10:07                                   ` Catalin Marinas
2006-08-19 11:20                                     ` Antonino A. Daplas
2006-08-19 13:25                                       ` Catalin Marinas
2006-08-19 10:27                                   ` Catalin Marinas
2006-08-19 10:32                                     ` Michal Piotrowski
2006-08-29 21:06         ` Catalin Marinas
2006-08-14 15:34   ` Catalin Marinas
2006-08-15 15:25     ` Catalin Marinas
2006-08-15 15:26       ` Catalin Marinas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6bffcb0e0608180528ocadc36ck8868ae1a33342bb9@mail.gmail.com \
    --to=michal.k.k.piotrowski@gmail.com \
    --cc=catalin.marinas@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®