3 ms·
I agree that formal verification isn't, by itself, some kind of panacea. Reading the paper, though, the effort did uncover some issues. Two examples, though the
by tyingq 5y ago
I agree that formal verification isn't, by itself, some kind of panacea. Reading the paper, though, the effort did uncover some issues. Two examples, though there are more:
"When proving invariants for page ownership used in the noninterference proofs, we identified a race condition in stage 2 page table updates"
"KCore initially did not check if a gfn was mapped before updating a VM’s stage 2 page tables, making it possible to overwrite existing mappings"
So mapping out the rules/flow in Coq, and then seeing what actually happened did uncover some flaws. As to whether the juice was worth the squeeze, I don't know this space well enough to comment.
- posix_me_less 5y agoYes, formal methods can be useful, they help uncover bugs. It's a debugging tool, albeit a very demanding one. For some software, it makes sense to use it. Real deployment of VMs has larger problems with security than not formally verified hypervisor so I think the answer for most hosting companies is "the juice is not worth the squeeze" here, the squeeze being the restriction to academic verified design. Hosting VMs is mostly about features and reliability. Those who need also real security, will host on their own HW and won't allow foreign VMs, so formally verified hypervisor is less of a requirement there too. It's a "nice to have".
- exdsq 5y agoIs it a debugging tool if the work is done upfront before writing code?
- posix_me_less 5y agoYes. Debugging tool reduces number of bugs in the product. Formal design specification and design verification can do that. And even with something lackluster like gdb, you may be forced to do some redesigning before writing more of new code.