> What I find very sad in all this is that you didnt mention the driver > that was triggering this bug.
Sorry, I was just trying to keep this thread focussed on one patch. The bug report that led me to this is publicly accessible at http://crosbug.com/35827. We have encountered the problem only once, on an Acer AC700 Chromebook that ran automated tests. The ethernet interface for the offending socket was provided by a USB-to-Ethernet dongle using the smsc95xx/usbnet module (v1.0.4). Don't get me wrong, I do understand the importance of finding the underlying cause of this... I just don't think I have much of a chance with one report. I can go through the above-mentioned module and see if something looks suspicious in the skb handling code if I can find the time. But on the other hand the fact remains that this condition is not handled well... not just for this particular case, but for all future kernel and driver bugs that may trigger it again. I am not trying to "hide" any issues, I am all for making them as visible as possible... but as Dave pointed out, kernel panics may not be the best way to do that either, and I think damage mitigation also has some value. The current code clearly does the worst of both worlds, so please let's just improve it one way or the other. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
