3 ms·

I'm not clear - do you want to protect the vmm driver in the host from attacks started by the rest of the host kernel? Or are you referring to attacks started b

• rwmj 10y ago
  I'm referring to a mistake in the kernel module corrupting some other in-kernel structures, especially if that can be triggered from guest code.
  • 4ad 10y ago
    There is no privilege separation between kernel modules. They all run in the same address space with the same CPU privilege. SELinux, seccomp, and all that protect a compromised user space thread in the host (responsible for running emulated guests, or one that provides virtual device support to guests) from other user space threads (other VMs). If there is a some problem in the KVM kernel module that stomps over memory, SELinux and seccomp can't do anything about it.
    • rwmj 10y ago
      Right, exactly the point I made up-thread (https://news.ycombinator.com/item?id=12700045 https://news.ycombinator.com/item?id=12700045).
  • brynet 10y ago
    OpenBSD has no kernel modules, everything compiled into the GENERIC kernel is expected to be using proper kernel interfaces, mucking around with kernel structures is a no-no. Nothing can really prevent driver bug causing a crash, this isn't a microkernel, but it can reduce exposure from userland, i.e: pledge restrictions on syscalls/ioctls/sysctls.