mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.18-rc4 00/10] Kernel memory leak detector 0.9
Date: Sat, 19 Aug 2006 11:27:57 +0100	[thread overview]
Message-ID: <b0943d9e0608190327h6ec3bb17wf32517af1fbf6d12@mail.gmail.com> (raw)
In-Reply-To: <6bffcb0e0608181549o3034398fob3763d3ce0869cfe@mail.gmail.com>

On 18/08/06, Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
> This is interesting. Is it too large?
> orphan pointer 0xfe09f000 (size 4194304):
>   c016cb9c: <__vmalloc_node>
>   c016cbb2: <__vmalloc>
>   c016cbc7: <vmalloc>
>   fdd3bbe1: <txInit>
>   fdd23b73: <init_jfs_fs>
>   c0149fea: <sys_init_module>

Looking at the code, I don't think it is too large. Anyway, it is just
a temporary false positive as it seems to only be present in some of
the files in your tarball.

> A large collection of false positives :)
> http://www.stardust.webpages.pl/files/o_bugs/kmemleak-0.9/ml_collection/ml1.tar

Thanks, but some of them look like real leaks :-) - delayacct_tsk_init
- I'll post a separate e-mail for this.

Have you seen any crashes or lockdep reports with the latest kmemleak patches?

-- 
Catalin

  parent reply	other threads:[~2006-08-19 10:27 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
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 [this message]
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=b0943d9e0608190327h6ec3bb17wf32517af1fbf6d12@mail.gmail.com \
    --to=catalin.marinas@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    /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®