On Tue, 2004-04-06 at 11:55, Alan Stern wrote: > In principle, yes. However... The kernel still has to process requests > correctly while the stack is partially deconstructed. It also has to > protect against userland helpers trying to pull things apart in the wrong > order.
This I agree with ... that's where the "robust to errors" statement comes in. I'm not claiming we currently are, merely that we have to be (regardless of ordered or disordered event propagation). > I'm not trying to say that anything you wrote was wrong -- just that the > situation is more complicated than you make it appear. Well, I think the principle is simple. The practice is less so ... I can still panic my test system by offlining the ext2 root filesystem in the middle of heavy stress. What I don't believe is that enforcing some kind of ordering can relieve us of the necessity of making the error paths robust. Since the largely hitherto untested error path becomes our main handler for forced disconnect, we're necessarily running into a lot of bugs that didn't show up before. However, they have always been bugs regardless of whether they got tripped. James ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
