On Mon, 14 May 2012, Oncaphillis wrote: > But I defonitely see changes in the memory chunk which is assumed to be > free. > The following shows the contents of the memory chunk which has been freed > recently > > proc_do_submiturb uurb->type==1:USBDEVFS_URB_TYPE_INTERRUPT alloc > tb:0xffff880077e7f138 > async_completed tb:0xffff880077e7f138[00][41] last > tb:0xffff88007a2b5a40[6b][6b] > free_async free tb:0xffff880077e7f138 > > proc_do_submiturb uurb->type==1:USBDEVFS_URB_TYPE_INTERRUPT alloc > tb:0xffff880077e7f138 > async_completed tb:0xffff880077e7f138[6b][6b] last > tb:0xffff880077e7f138[6b][6b] > free_async free tb:0xffff880077e7f138 What is the value of urb->actual_length in async_completed()? > proc_do_submiturb uurb->type==3:USBDEVFS_URB_TYPE_BULK alloc > tb:0xffff88007a2b5a40 > async_completed tb:0xffff88007a2b5a40[00][41] last > tb:0xffff880077e7f138[00][41] <= 'last tb' is assumed to be freed in the > last free_async > free_async free tb:0xffff88007a2b5a40 Does the same thing happen on different computers? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
