site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com User-agent: Thunderbird 1.5.0.8 (Macintosh/20061025) On Nov 22, 2006, at 6:04 PM, Michael Smith wrote: Stephane wrote: It turned out to be a copyin of a bigger size than required. = Mike _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... Stephane wrote: When you do some bad things in your Kernel Extension (such as writing where you should not, reading a bit too far in buffers, etc...), should a Kernel Panic occur in your Kernel Extension or can it occur later? It depends on what you damage. If you read/write completely out of bounds, your code will fail. But if you destroy a pointer belonging to someone else, there is no way for the hardware/kernel to know a) that that's what you're doing, or b) to blame you when some other code attempts to use it. It could be cool if there was a Kernel simulator with memory protection... Protection of what? Read/write memory in the kernel map is freely writable by any code within the kernel; this is what being a "monolithic" kernel is all about. Given how much vilifiction Darwin has received for being a "microkernel" because we "all know" how inefficient they are, I see this rapidly becoming amusing. This email sent to site_archiver@lists.apple.com