Greg et al. I'm considering adding more error checking to the descriptor parsing routines in core/config.c. Especially I want to sort the interface pointers in order by bInterfaceNumber and sort the altsettings for each interface by bAlternateSetting -- since the device isn't necessarily going to transmit them in numerical order.
But doing that raises the possibilities that some interface descriptor might have bInterfaceNumber not in the range 0..(bNumInterfaces-1), or there might be two descriptors with the same bInterfaceNumber and bAlternateSetting values, or there might not be any descriptors for a particular bInterfaceNumber/bAlternateSetting combination. Checking for these things is important, since the mere act of plugging in a device with descriptor errors like this might crash the kernel. The question is, what should the code do when it encounters these sorts of errors? Alan Stern ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
