Re: [Linux-usb-users] usblp error handling broken

2007-05-09 Thread Greg KH
On Mon, May 07, 2007 at 01:35:27PM +0200, Jochen Karrer wrote:
 Hi,
 The error handling in usblp_write is broken.

Try bringing this up on the linux-usb-devel mailing list.  The
developers there should be able to help you out.

Also please note which kernel version you are looking at.

thanks,

greg k-h

-
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-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users


[Linux-usb-users] usblp error handling broken

2007-05-08 Thread Jochen Karrer
Hi,
The error handling in usblp_write is broken. If I use blocking IO and
any error happens which makes writeurb_status nonzero the usblp driver
will end up in an endless loop sending status requests to the printer.
The only way to leave this loop is to unplug the printer because this
sets usblp-present to zero.
This is no wonder because the error handler simply continues the loop
without trying again to send data over the USB. The writeurb status will
never change.

Here a simplified version of my problem:

while(writecount  count) {
...
if (usblp-writeurb-status != 0) {
err = usblp_check_status(usblp, err);
continue;
}
...
err = usb_submit_urb(usblp-writeurb, GFP_KERNEL);
...
}

How is the intended error behaviour ? Should usblp_write simply retry
forever or should the system call return with an error ? Should there be
a retry limit ?

Jochen



-
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-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users