Re:QEMU: user-to-root privesc inside VM via bad translation ...
by hueving on Wednesday March 22, 2017 @05:11AM
(#13929463)
If you really wanted to fish for a "told ya so", someone could just point out that by eliminating all of those other classes of bugs, developers could have spent more time looking for logic errors.
[ Parent
| on HN ]
Re:QEMU: user-to-root privesc inside VM via bad translation ...
by empath75 on Wednesday March 22, 2017 @08:59AM
(#13930509)
Will you have time for that after fighting the borrow checker?
Re:QEMU: user-to-root privesc inside VM via bad translation ...
by simion314 on Wednesday March 22, 2017 @09:17AM
(#13930629)
If a developer finishes his task he will be given a new task, I don't think you will get a task "go and review our code again for weird logic errors" you will be sent to add a new feature or fix a bug, so you will work on that and create a few new bugs.
Re:QEMU: user-to-root privesc inside VM via bad translation ...
by nullc on Wednesday March 22, 2017 @07:23AM
(#13930039)
I got that while trolling Rust developers a bit on this point, and had to concede-- it's a fair point.
I do think that rust doesn't (yet) have enough affordances for formal verification of algorithmic correctness-- but if you're not chasing memory safety you have more time to deal with other issues.