Re:The mysterious case of the Linux Page Table Isolation pat...
by baybal2 on Tuesday January 02, 2018 @07:12AM
(#16051424)
>Intel CPU do some speculative execution on priviledged data from unpriviledged code, including from (at least some and at least part of) separate following instructions.
That was known since pentium 3 times, I wonder why nobody thought of this as a wonderful exploit target before
>I'm 90% convinced there is no way Intel managed to close all the side-channels on such a complex architecture
This is why one should not use verilog and run formal validation of all and everything related to hdl code
Re:The mysterious case of the Linux Page Table Isolation pat...
by orbifold on Tuesday January 02, 2018 @07:58AM
(#16051585)
What should one use instead? VHDL, Bluespec, Chisel? I don‘t know of any solution that makes verification significantly easier compared to SystemVerilog.
Re:The mysterious case of the Linux Page Table Isolation pat...
by baybal2 on Tuesday January 02, 2018 @08:25AM
(#16051691)
It will be VHDL for the reason it removes a lot undefined behaviours by design.
Tooling support for VHDL is lacking thought, any big company with in house formal verification must have their own tooling...
Re:The mysterious case of the Linux Page Table Isolation pat...
by JdeBP on Tuesday January 02, 2018 @09:53AM
(#16052118)
What undefined behaviours are those?
Re:The mysterious case of the Linux Page Table Isolation pat...
by wastewaste on Tuesday January 02, 2018 @10:02AM
(#16052175)
tricky grammar. You mean formal, mathematical verification instead of simulation, I suppose, but I am not aware of any different method.
Re:The mysterious case of the Linux Page Table Isolation pat...
by baybal2 on Tuesday January 02, 2018 @11:42AM
(#16053021)
Yes, mathematical verification. Normally, for an any much expensive tape out a partial mathematical verification is done with tooling on hand in addition to brute force simulation.
Ideally, a much closer to complete verification should be done in addition to simulation, like a mathematical proof that register content will never be like set A if inputs are set B
Note that under Linux x64 IIRC the whole physical memory is mapped in kernel pages... playing with some adjusting variables, if this theory is correct, I don't see why we could not read all of it. Might be the same under Windows.
I've not checked in depth yet but it could match with all the technical facts we have: very important bug for which the semi-rushed workaround with high perf impact will be backported; affect general purpose OSes but IIRC does not affect some hypervisors (I guess they already do not map at all the pages of other systems while one is running), does not affect AMD (or maybe at least not this way and KPTI can not fix it for them) because of their microarch, involves data leak.