Well, I don't know so much about the linux-usb code. I got no idea where this could happen. The backtrace doesn't give me usefull informations.
It will if you use "ksymoops" ... go from there to find the line of source code that showed the problem. It'd also be good to build your kernel with all debugging options enabled.
OK, the problem is that double-free doesn't always oops where it happens.
Slab poisoning helps, it tells you when code is referencing data that's been freed ... it poisons the memory on the first free.
------------------------------------------------------- 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
