linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Marcel Holtmann <marcel@holtmann.org>,
	Gustavo Padovan <gustavo@padovan.org>,
	Johan Hedberg <johan.hedberg@gmail.com>
Cc: Linux Bluetooth mailing list <linux-bluetooth@vger.kernel.org>
Subject: Memory leak in btusb
Date: Mon, 25 May 2015 16:01:13 -0500	[thread overview]
Message-ID: <55638D99.5000704@lwfinger.net> (raw)

Hi,

While using kmemleak to check for memory leaks in a wireless driver, I noticed 
the following stack traceback for a leak in btusb:

<ffffffff8160257e>] __alloc_skb+0x7e/0x2b0
[<ffffffffa06029d6>] btusb_recv_intr+0x136/0x180 [btusb]
[<ffffffffa0602ad8>] btusb_intr_complete+0xb8/0x150 [btusb]
[<ffffffff8156ccb2>] __usb_hcd_giveback_urb+0x72/0x120

To eliminate a false positive, I unloaded the driver and got the following for 
the virtual address:

[<ffffffff8160257e>] __alloc_skb+0x7e/0x2b0
[<ffffffffa06029d6>] 0xffffffffa06029d6
[<ffffffffa0602ad8>] 0xffffffffa0602ad8
[<ffffffff8156ccb2>] __usb_hcd_giveback_urb+0x72/0x120

The source is from wireless-drivers-next.git with pulls from bluetooth-next.git 
and Torvalds mainline git repo that were done on May 25. The source includes 
commit 04b8c8143d46453a443ac32bfcd76ec952605765 with the subject "Bluetooth: 
btusb: fix Realtek suspend/resume".

The Bluetooth device in use is made by Intel with USB ID 8087:07dc.

Thanks,

Larry

             reply	other threads:[~2015-05-25 21:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-25 21:01 Larry Finger [this message]
2015-06-06  6:20 ` Memory leak in btusb Marcel Holtmann
2015-06-06  6:23 ` Marcel Holtmann
2015-06-06 16:03   ` Larry Finger
2015-06-06 16:37 ` Marcel Holtmann
2015-06-06 18:03   ` Larry Finger
2015-06-06 18:31     ` Marcel Holtmann
2015-06-06 21:31       ` Larry Finger
2015-06-06 21:38       ` Larry Finger
2015-06-06 22:54         ` Marcel Holtmann

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=55638D99.5000704@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=gustavo@padovan.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.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).