On 08/23/2013 05:07 PM, Alan Stern wrote:
On Fri, 23 Aug 2013, Xenia Ragiadakou wrote:
Martin is right; the BOS descriptors are leaked in
usb_reset_and_verify_device(). We need to store the old descriptor,
compare it with the new one following the reset, and delete one of them
afterward. I
On Mon, 26 Aug 2013, Xenia Ragiadakou wrote:
I will send a patch as RFC because i am not quite familiar and because i
have a problem to run kmemleak effectively (i can only scan for a few
seconds, although i have set all necessary kmemleak configuration, i
have not figured out why yet).
On 08/14/2013 08:24 AM, Sarah Sharp wrote:
On Fri, Aug 09, 2013 at 05:14:48PM -0400, Alan Stern wrote:
On Fri, 9 Aug 2013, Greg KH wrote:
On Thu, Aug 08, 2013 at 10:07:19PM +0200, Martin MOKREJŠ wrote:
Hi,
I get plenty of these in /sys/kernel/debug/kmemleak:
unreferenced object
On Fri, 23 Aug 2013, Xenia Ragiadakou wrote:
Martin is right; the BOS descriptors are leaked in
usb_reset_and_verify_device(). We need to store the old descriptor,
compare it with the new one following the reset, and delete one of them
afterward. I haven't had time to fix this.
I'll
On Tue, 13 Aug 2013, Sarah Sharp wrote:
Martin is right; the BOS descriptors are leaked in
usb_reset_and_verify_device(). We need to store the old descriptor,
compare it with the new one following the reset, and delete one of them
afterward. I haven't had time to fix this.
I'll put
On Thu, Aug 08, 2013 at 10:07:19PM +0200, Martin MOKREJŠ wrote:
Hi,
I get plenty of these in /sys/kernel/debug/kmemleak:
unreferenced object 0x88019f675268 (size 32):
comm usb-storage, pid 11411, jiffies 4310515592 (age 1538.100s)
hex dump (first 32 bytes):
05 0f 16 00 02 07
On Fri, 9 Aug 2013, Greg KH wrote:
On Thu, Aug 08, 2013 at 10:07:19PM +0200, Martin MOKREJŠ wrote:
Hi,
I get plenty of these in /sys/kernel/debug/kmemleak:
unreferenced object 0x88019f675268 (size 32):
comm usb-storage, pid 11411, jiffies 4310515592 (age 1538.100s)
hex
