On Sat, 5 May 2007, Chris Rankin wrote:
> --- Alan Stern <[EMAIL PROTECTED]> wrote:
> > However it is usually the same endpoint number and the same device (even
> > if the device number changes)? In that case we can tell the code where to
> > look for errors, because we will always know when that particular endpoint
> > file is created and when it is destroyed.
>
> I think it's safe to say "yes, it's always ep84" here, provided I am trying
> to provoke the bug
> with winecfg. I have obviously seen this bug in a few other scenarios as well
> over the months,
> e.g. from the report in bugzilla:
Tejun, would this help? We could create and export a pointer to kobject
from the sysfs core, say:
struct kobject *testptr;
EXPORT_SYMBOL(testptr);
Then I could add something to the USB code which would set testptr to
point at the kobject embedded in the "ep84" device when it was created,
and would clear testptr when the device was released. This way you could
write a debugging patch for sysfs to monitor the sd associated with
testptr for nefarious changes.
Alan Stern
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
