Messages in this thread | | | Date | Fri, 30 Apr 2004 08:01:46 +0200 | From | Matthias Schniedermeyer <> | Subject | Re: [PATCH] Blacklist binary-only modules lying about their license |
| |
> You have pointed out an interesting point in another email. I have to > agree that, technically, thunking to BIOS code also taints the kernel, > because it, too, is a black box which could corrupt the kernel. What do > others have to say about that?
There is more.
Not executing external code, but trusting external data.
e.g. The symbios(*1)-SCSI-driver only shows devices enabled in its BIOS. This information is stored in a little NVRAM-chip(*2) and the driver uses this data, including bus-speed settings and the like. At least i (had/have*3) trouble with this "feature"!
*1: NCR, Symbios-Logic, LSI-Logic, whatever they are called today *2: You need anything "bigger" than the 810-model *3: I'm not sure if i still have trouble with this feature because i haven't changed the setup in my computer for 3 years, it MAY be that i still use a workaround for this feature. My next computer won't have SCSI anymore, so i don't care if i still use a workaround.
Bis denn
-- Real Programmers consider "what you see is what you get" to be just as bad a concept in Text Editors as it is in women. No, the Real Programmer wants a "you asked for it, you got it" text editor -- complicated, cryptic, powerful, unforgiving, dangerous.
- 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/
| |