From: Alexey Fisher <bug-track-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org>
To: Pekka Enberg <penberg-bbCR+/B0CizivPeTLB3BmA@public.gmane.org>
Cc: Kernel Testers List
<kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>
Subject: Re: 60 memory leaks.. or is it some thing wrong with kmemleak?
Date: Tue, 14 Jul 2009 10:28:56 +0200 [thread overview]
Message-ID: <4A5C41C8.7040904@fisher-privat.net> (raw)
In-Reply-To: <84144f020907140019g511723dctb541f6333d1a082b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Pekka,
i updated now to git 2.6.31-rc3 and now i have
"kmemleak: 76 new suspected memory leaks"
ext4 and control group still there.
Pekka Enberg schrieb:
> Hi Alexey,
>
> [ Lets cc Catalin. ]
>
> On Tue, Jul 14, 2009 at 9:08 AM, Alexey
> Fisher<bug-track-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org> wrote:
>> Hallo all,
>> i enabled kmemleak and now i get a lot of them...
>
> Which kernel version is this? You almost definitely want to try out
> 2.6.31-rc3 which has tons of bug fixes to kmemleak.
>
>> i do not know if this are real or some noise..
>> most of the about mounting ext4
>>
>> unreferenced object 0xffff880133c63800 (size 1024):
>> comm "exe", pid 1521, jiffies 4294894652
>> backtrace:
>> [<ffffffff810f8f36>] create_object+0x126/0x2b0
>> [<ffffffff810f91d5>] kmemleak_alloc+0x25/0x60
>> [<ffffffff810f32a3>] __kmalloc+0x113/0x200
>> [<ffffffff811aa061>] ext4_mb_init+0x1b1/0x570
>> [<ffffffff8119b3d2>] ext4_fill_super+0x1de2/0x26d0
>> [<ffffffff810fe40f>] get_sb_bdev+0x16f/0x1b0
>> [<ffffffff811912f3>] ext4_get_sb+0x13/0x20
>> [<ffffffff810fdee6>] vfs_kern_mount+0x76/0x180
>> [<ffffffff810fe05d>] do_kern_mount+0x4d/0x120
>> [<ffffffff81115e17>] do_mount+0x307/0x880
>> [<ffffffff8111641f>] sys_mount+0x8f/0xe0
>> [<ffffffff8100b66b>] system_call_fastpath+0x16/0x1b
>> [<ffffffffffffffff>] 0xffffffffffffffff
>> unreferenced object 0xffff8801334db0c0 (size 192):
>> comm "exe", pid 1521, jiffies 4294894652
>> backtrace:
>> [<ffffffff810f8f36>] create_object+0x126/0x2b0
>> [<ffffffff810f91d5>] kmemleak_alloc+0x25/0x60
>> [<ffffffff810f32a3>] __kmalloc+0x113/0x200
>> [<ffffffff811aa061>] ext4_mb_init+0x1b1/0x570
>> [<ffffffff8119b3d2>] ext4_fill_super+0x1de2/0x26d0
>> [<ffffffff810fe40f>] get_sb_bdev+0x16f/0x1b0
>> [<ffffffff811912f3>] ext4_get_sb+0x13/0x20
>> [<ffffffff810fdee6>] vfs_kern_mount+0x76/0x180
>> [<ffffffff810fe05d>] do_kern_mount+0x4d/0x120
>> [<ffffffff81115e17>] do_mount+0x307/0x880
>> [<ffffffff8111641f>] sys_mount+0x8f/0xe0
>> [<ffffffff8100b66b>] system_call_fastpath+0x16/0x1b
>> [<ffffffffffffffff>] 0xffffffffffffffff
>>
>>
>> and other seems like about control group:
>>
>>
>> unreferenced object 0xffff88013b852440 (size 544):
>> comm "swapper", pid 0, jiffies 4294892296
>> backtrace:
>> [<ffffffff810f8f36>] create_object+0x126/0x2b0
>> [<ffffffff810f91d5>] kmemleak_alloc+0x25/0x60
>> [<ffffffff810f24f3>] kmem_cache_alloc+0xf3/0x170
>> [<ffffffff8121deff>] idr_pre_get+0x5f/0x90
>> [<ffffffff810898c5>] get_new_cssid+0x65/0x120
>> [<ffffffff8174f7a3>] cgroup_init+0x6f/0x109
>> [<ffffffff8173ad21>] start_kernel+0x3a6/0x3ca
>> [<ffffffff8173a315>] x86_64_start_reservations+0x125/0x129
>> [<ffffffff8173a3fd>] x86_64_start_kernel+0xe4/0xeb
>> [<ffffffffffffffff>] 0xffffffffffffffff
>> unreferenced object 0xffff88013b852660 (size 544):
>> comm "swapper", pid 0, jiffies 4294892296
>> backtrace:
>> [<ffffffff810f8f36>] create_object+0x126/0x2b0
>> [<ffffffff810f91d5>] kmemleak_alloc+0x25/0x60
>> [<ffffffff810f24f3>] kmem_cache_alloc+0xf3/0x170
>> [<ffffffff8121deff>] idr_pre_get+0x5f/0x90
>> [<ffffffff810898c5>] get_new_cssid+0x65/0x120
>> [<ffffffff8174f7a3>] cgroup_init+0x6f/0x109
>> [<ffffffff8173ad21>] start_kernel+0x3a6/0x3ca
>> [<ffffffff8173a315>] x86_64_start_reservations+0x125/0x129
>> [<ffffffff8173a3fd>] x86_64_start_kernel+0xe4/0xeb
>> [<ffffffffffffffff>] 0xffffffffffffffff
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>>
> --
> To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-07-14 8:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 6:08 60 memory leaks.. or is it some thing wrong with kmemleak? Alexey Fisher
[not found] ` <4A5C20E5.6010203-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org>
2009-07-14 7:19 ` Pekka Enberg
[not found] ` <84144f020907140019g511723dctb541f6333d1a082b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-07-14 8:28 ` Alexey Fisher [this message]
[not found] ` <4A5C41C8.7040904-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org>
2009-07-14 9:39 ` Catalin Marinas
[not found] ` <1247564356.28240.30.camel-hhZApKj8DF/YkXV2EHHjLW3o5bpOHsLO@public.gmane.org>
2009-07-14 9:52 ` [PATCH] x86: _edata should include all .data.* sections on X86_64 Catalin Marinas
[not found] ` <1247565175.28240.37.camel-hhZApKj8DF/YkXV2EHHjLW3o5bpOHsLO@public.gmane.org>
2009-07-14 10:13 ` Alexey Fisher
[not found] ` <4A5C5A59.5080304-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org>
2009-07-14 10:31 ` Catalin Marinas
[not found] ` <1247567499.28240.48.camel-hhZApKj8DF/YkXV2EHHjLW3o5bpOHsLO@public.gmane.org>
2009-07-14 10:37 ` Alexey Fisher
[not found] ` <4A5C5FD0.3020204-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org>
2009-07-14 12:26 ` ext4 memory leak (was Re: [PATCH] x86: _edata should include all .data.* sections on X86_64) Catalin Marinas
2009-07-15 8:03 ` Aneesh Kumar K.V
2009-07-15 8:54 ` Alexey Fisher
[not found] ` <4A5D9939.3000500-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org>
2009-07-18 11:55 ` Ingo Molnar
[not found] ` <20090718115556.GA31007-X9Un+BFzKDI@public.gmane.org>
2009-07-18 13:30 ` Alexey Fisher
[not found] ` <4A61CE59.3030905-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org>
2009-07-18 22:44 ` Catalin Marinas
2009-07-18 22:33 ` Catalin Marinas
2009-07-15 10:33 ` Catalin Marinas
2009-07-14 12:42 ` [PATCH] x86: _edata should include all .data.* sections on X86_64 Catalin Marinas
2009-07-16 20:23 ` Sam Ravnborg
2009-07-18 20:29 ` [kmemleak] 60 wornings on sysfs_new_dirent+0x10c Alexey Fisher
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=4A5C41C8.7040904@fisher-privat.net \
--to=bug-track-m18mab7tlt0ycq4ww13eyl6hyfs7nttn@public.gmane.org \
--cc=catalin.marinas-5wv7dgnIgG8@public.gmane.org \
--cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=penberg-bbCR+/B0CizivPeTLB3BmA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).