...this allows loading code from ram for execution in flash. this is what all bootloaders do. so you can argue about what constitutes harvard but the fact remains code from ee or ram CAN be executed. its mostly a timing issue.
afaik no one has been able to do this in windows since 98.
and btw c girls should not even try due to opcode timing issues usually associated with compiled code. at least with gcc from what i can tell. maybe inline asm tricks but i doubt it.
Windows drivers can spinlock a CPU as well, so I'm not sure this is a uniquely Linux thing, but I'm not a kernel hacker or driver developer either. Is there anything in the kernel that prevents execution of particular opcodes on either platform, once you're in kernel-land? It was my assumption that code at that level was free to do just about anything it wants to, which is what makes bugs (and especially malicious code!) there so vile.