From: Tomas Targownik <ttargownik@geicp.com>
To: "Gustavo F. Padovan" <padovan@profusion.mobi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Memory leak on failed connection attempt
Date: Tue, 14 Jun 2011 17:03:24 +1000 [thread overview]
Message-ID: <1308035004.1926.611.camel@rnd3> (raw)
In-Reply-To: <20110602135720.GB2790@joana>
On Thu, 2011-06-02 at 10:57 -0300, Gustavo F. Padovan wrote:
> Hi Tomas,
> ...
> Can you try an upstream kernel and check if this still happens? 2.6.32 is
> quite old.
Hi Gustavo, and thank you for the advice. I've managed to port my device
to linux-2.6.39.1, and have also upgraded to the latest Bluez4 v4.94,
and I am still seeing the leak on failed connection attempts. The output
shown by 'cat /sys/kernel/debug/kmemleak' has changed slightly, however-
unreferenced object 0xc2ce0600 (size 512):
comm "softirq", pid 0, jiffies 4294956138 (age 56.420s)
hex dump (first 32 bytes):
00 01 10 00 00 02 20 00 00 00 00 00 7a a5 02 94 ...... .....z...
0a 00 00 00 09 00 00 01 01 01 00 00 00 00 00 00 ................
backtrace:
[<c00da3ac>] create_object+0x120/0x210
[<c021d058>] kmemleak_alloc+0x40/0x74
[<c00d7cd4>] kmem_cache_alloc+0x9c/0xd0
[<bf055f54>] hci_conn_add+0x30/0x268 [bluetooth]
[<bf056504>] hci_connect+0x1d4/0x3e8 [bluetooth]
[<bf0637f8>] l2cap_do_connect+0xfc/0x304 [bluetooth]
[<bf066c84>] l2cap_sock_connect+0x180/0x1dc [bluetooth]
[<c01a9458>] sys_connect+0x74/0x98
[<c0070fc0>] ret_fast_syscall+0x0/0x2c
[<ffffffff>] 0xffffffff
unreferenced object 0xc2c4ee00 (size 512):
comm "softirq", pid 0, jiffies 4294957663 (age 41.170s)
hex dump (first 32 bytes):
00 01 10 00 00 02 20 00 00 00 00 00 7a a5 02 94 ...... .....z...
0a 00 00 00 09 00 00 01 01 01 00 00 00 00 00 00 ................
backtrace:
[<c00da3ac>] create_object+0x120/0x210
[<c021d058>] kmemleak_alloc+0x40/0x74
[<c00d7cd4>] kmem_cache_alloc+0x9c/0xd0
[<bf055f54>] hci_conn_add+0x30/0x268 [bluetooth]
[<bf056504>] hci_connect+0x1d4/0x3e8 [bluetooth]
[<bf0637f8>] l2cap_do_connect+0xfc/0x304 [bluetooth]
[<bf066c84>] l2cap_sock_connect+0x180/0x1dc [bluetooth]
[<c01a9458>] sys_connect+0x74/0x98
[<c0070fc0>] ret_fast_syscall+0x0/0x2c
[<ffffffff>] 0xffffffff
Can anybody else confirm this?
Thank you,
Tomas Targownik
next prev parent reply other threads:[~2011-06-14 7:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 6:48 Memory leak on failed connection attempt Tomas Targownik
2011-06-02 13:57 ` Gustavo F. Padovan
2011-06-14 7:03 ` Tomas Targownik [this message]
2011-06-15 23:22 ` Tomas Targownik
2011-06-16 21:26 ` Gustavo F. Padovan
2011-06-20 3:15 ` Tomas Targownik
2011-06-23 22:34 ` Tomas Targownik
2011-06-30 5:22 ` Gustavo F. Padovan
2011-07-04 1:40 ` Tomas Targownik
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=1308035004.1926.611.camel@rnd3 \
--to=ttargownik@geicp.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=padovan@profusion.mobi \
/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