On Thu, Nov 29, 2007 at 03:25:04PM -0500, Mark Lord wrote: > (resending .. somebody trimmed the CC: list earlier) > > Greg KH wrote: >>>>> Mark Lord wrote: >>>>>> .. >>>>>> >>>>>> While doing insert/remove (quickly) tests on USB, >>>>>> I managed to trigger an Oops on 2.6.23.8 on a call >>>>>> to strlen() in make_class_name(). > ... > >> I'll hold off on adding this patch for now. > .. > > Why? > > Bugs that result in Oops in core code (class.c) can bite > just about any subsystem that does hotplug, and should get > prompt attention. Or so one might think.
And they have, the 2.6.24 kernel should have the correct fix for this problem, right? The fact that you oopsed out in this function enabled people to find and fix the problem already. Adding a BUG_ON() does the same exact thing :) So again, the problem is in the higher up scsi layer, and that is where the problem should already be fixed. Don't add code to lower layers to paper over bugs elsewhere. thanks, greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/