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 00/10] Kernel memory leak detector 0.8
Date: Tue, 11 Jul 2006 18:02:59 +0200 [thread overview]
Message-ID: <6bffcb0e0607110902u4e24a4f2jc6acf2eb4c3bae93@mail.gmail.com> (raw)
In-Reply-To: <b0943d9e0607110844m6278da6crdc03bccce420da1d@mail.gmail.com>
On 11/07/06, Catalin Marinas <catalin.marinas@gmail.com> wrote:
> > orphan pointer 0xc6113bec (size 28):
> > c017392a: <__kmalloc_track_caller>
> > c01631b1: <__kzalloc>
> > c010b7d7: <legacy_init_iomem_resources>
> > c010b89c: <request_standard_resources>
> > c0100b8b: <do_initcalls>
> > c0100c3d: <do_basic_setup>
> > c0100cdb: <init>
>
> That's a real leak. I posted a patch last night that solves this issue
> - http://lkml.org/lkml/2006/7/10/370
Thanks.
>
> > This is most common
> > orphan pointer 0xf5a6fd60 (size 39):
> > c0173822: <__kmalloc>
> > c01df500: <context_struct_to_string>
> > c01df679: <security_sid_to_context>
> > c01d7eee: <selinux_socket_getpeersec_dgram>
> > f884f019: <unix_get_peersec_dgram>
> > f8850698: <unix_dgram_sendmsg>
> > c02a88c2: <sock_sendmsg>
> > c02a9c7a: <sys_sendto>
>
> Looking at the call trace, the pointer to the memory allocated in
> context_struct_to_string() is stored in the "cb" variable in struct
> sk_buff (argument passed to selinux_socket_getpeersec_dgram from
> unix_get_peersec_dgram).
>
> This pointer should be found when scanning the "struct sk_buff"
> blocks, unless you also get a comparable number of "struct sk_buff"
> reports (from __alloc_skb). If not, it might be a real leak.
So if we got 3970
orphan pointer 0xf5a6fd60 (size 39):
c0173822: <__kmalloc>
c01df500: <context_struct_to_string>
c01df679: <security_sid_to_context>
c01d7eee: <selinux_socket_getpeersec_dgram>
f884f019: <unix_get_peersec_dgram>
f8850698: <unix_dgram_sendmsg>
c02a88c2: <sock_sendmsg>
c02a9c7a: <sys_sendto>
and 4673
orphan pointer 0xf4249488 (size 29):
c0173822: <__kmalloc>
c01df500: <context_struct_to_string>
c01df679: <security_sid_to_context>
c01d7eee: <selinux_socket_getpeersec_dgram>
f884f019: <unix_get_peersec_dgram>
f8850698: <unix_dgram_sendmsg>
c02a8d68: <do_sock_write>
c02a8e85: <sock_aio_write>
It's not a memleak?
http://www.stardust.webpages.pl/files/o_bugs/kml/ml3.txt
>
> --
> Catalin
>
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)
next prev parent reply other threads:[~2006-07-11 16:03 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 22:09 Catalin Marinas
2006-07-10 22:09 ` [PATCH 01/10] Base support for kmemleak Catalin Marinas
2006-07-10 22:09 ` [PATCH 02/10] Some documentation " Catalin Marinas
2006-07-10 22:09 ` [PATCH 03/10] Add the memory allocation/freeing hooks " Catalin Marinas
2006-07-11 6:17 ` Pekka Enberg
2006-07-11 7:59 ` Catalin Marinas
2006-07-10 22:10 ` [PATCH 04/10] Modules support " Catalin Marinas
2006-07-10 22:10 ` [PATCH 05/10] Add kmemleak support for i386 Catalin Marinas
2006-07-10 22:10 ` [PATCH 06/10] Add kmemleak support for ARM Catalin Marinas
2006-07-10 22:10 ` [PATCH 07/10] Remove some of the kmemleak false positives Catalin Marinas
2006-07-11 6:49 ` Pekka Enberg
2006-07-11 8:18 ` Catalin Marinas
2006-07-10 22:10 ` [PATCH 08/10] Keep the __init functions after initialization Catalin Marinas
2006-07-10 22:10 ` [PATCH 09/10] Simple testing for kmemleak Catalin Marinas
2006-07-10 22:11 ` [PATCH 10/10] Update the MAINTAINERS file " Catalin Marinas
2006-07-11 12:27 ` [PATCH 00/10] Kernel memory leak detector 0.8 Michal Piotrowski
2006-07-11 12:46 ` Michal Piotrowski
2006-07-11 12:51 ` Michal Piotrowski
2006-07-11 13:00 ` Catalin Marinas
2006-07-11 13:09 ` Michal Piotrowski
2006-07-12 9:57 ` Joseph Fannin
2006-07-12 10:38 ` Catalin Marinas
2006-07-12 10:49 ` Michal Piotrowski
2006-07-14 2:22 ` Horst von Brand
2006-07-11 12:56 ` Catalin Marinas
2006-07-11 13:17 ` Michal Piotrowski
2006-07-11 13:28 ` Catalin Marinas
2006-07-11 13:49 ` Michal Piotrowski
2006-07-11 14:02 ` Catalin Marinas
2006-07-11 15:02 ` Michal Piotrowski
2006-07-11 15:44 ` Catalin Marinas
2006-07-11 16:02 ` Michal Piotrowski [this message]
2006-07-11 16:31 ` Catalin Marinas
2006-07-11 17:00 ` Michal Piotrowski
2006-07-11 21:54 ` Catalin Marinas
2006-07-12 11:35 ` Michal Piotrowski
2006-07-12 16:17 ` Catalin Marinas
2006-07-12 22:55 ` Michal Piotrowski
2006-07-13 16:35 ` Catalin Marinas
2006-07-13 19:14 ` Michal Piotrowski
2006-07-14 14:53 ` Catalin Marinas
2006-07-12 13:19 ` Michal Piotrowski
2006-07-12 14:37 ` Catalin Marinas
2006-07-12 15:33 ` Michal Piotrowski
2006-07-12 16:12 ` Catalin Marinas
2006-07-12 10:33 ` Catalin Marinas
2006-07-12 18:46 ` Xiaolan Zhang
2006-07-13 18:52 ` Xiaolan Zhang
2006-07-13 19:17 ` Michal Piotrowski
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=6bffcb0e0607110902u4e24a4f2jc6acf2eb4c3bae93@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®