From: Alexey Fisher <bug-track@fisher-privat.net>
To: Kernel Testers List <kernel-testers@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 60 memory leaks.. or is it some thing wrong with kmemleak?
Date: Tue, 14 Jul 2009 08:08:37 +0200 [thread overview]
Message-ID: <4A5C20E5.6010203@fisher-privat.net> (raw)
Hallo all,
i enabled kmemleak and now i get a lot of them...
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
next reply other threads:[~2009-07-14 6:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 6:08 Alexey Fisher [this message]
2009-07-14 7:19 ` Pekka Enberg
2009-07-14 8:28 ` Alexey Fisher
2009-07-14 9:39 ` Catalin Marinas
2009-07-14 9:52 ` [PATCH] x86: _edata should include all .data.* sections on X86_64 Catalin Marinas
2009-07-14 10:13 ` Alexey Fisher
2009-07-14 10:31 ` Catalin Marinas
2009-07-14 10:37 ` Alexey Fisher
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
2009-07-18 11:55 ` Ingo Molnar
2009-07-18 13:30 ` Alexey Fisher
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 12:06 ` [tip:x86/urgent] x86: Include all of .data.* sections in _edata on 64-bit tip-bot for Catalin Marinas
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=4A5C20E5.6010203@fisher-privat.net \
--to=bug-track@fisher-privat.net \
--cc=kernel-testers@vger.kernel.org \
--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®