linux-kernel - Re: 2.6.23-mm1

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

Date:	Sun, 14 Oct 2007 11:39:14 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	"Torsten Kaiser" <just.for.lkml@...glemail.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.23-mm1

On Sun, 14 Oct 2007 13:54:26 +0200 "Torsten Kaiser" <just.for.lkml@...glemail.com> wrote:

> > The page-owner code can pinpoint a leak source.  See
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23/2.6.23-mm1/broken-out/page-owner-tracking-leak-detector.patch
> >
> > Enable CONFIG_DEBUG_SLAB_LEAK, check out /proc/slab_allocators
> 
> Did that. The output of /proc/page_owner is ~350Mb, gzipped still ~7Mb.
> 
> Taking only the first line from each stackdump it shows the following counts:
>
> ...
>
>  354042 [0xffffffff80266373] mempool_alloc+83

This one is suspicious.  Can you find the whole record for it?

The other info shows a tremendous memory leak, not via slab.  Looks like
someone is running alloc_pages() directly and isnb't giving them back.

-
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/