Hi Larry, > 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. does this only happen with the Intel device or with all Bluetooth USB dongles? Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
