Messages in this thread | | | Date | Mon, 03 May 2004 20:50:50 +0200 | From | Stefan Smietanowski <> | Subject | Re: What does tainting actually mean? |
| |
Hi Pavel.
>>Is that true? We can see where the oops occurs. If it's in the >>module, nothing more needs to be said. If it's in the kernel itself, >>we can check our source. We could check all the calls the module > > > We *could* do it, but it would take too much time and we > have better stuff to do.
And we don't know if that module didn't overwrite memory (nVidia ..) or anything else either. The the oops is really useless.
Of course, those cases are difficult to debug ANYWAY even if you have the source but if it's binary you can't do squat.
// Stefan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |