4 ms·

Because it wasn't an updated driver, it was a malformed blob config. https://www.youtube.com/watch?v=ZHrayP-Y71Q https://www.youtube.com/watch?v=ZHrayP-Y71Q ht

Because it wasn't an updated driver, it was a malformed blob config. https://www.youtube.com/watch?v=ZHrayP-Y71Q https://www.youtube.com/watch?v=ZHrayP-Y71Q https://www.youtube.com/watch?v=wAzEJxOo1ts https://www.youtube.com/watch?v=wAzEJxOo1ts That verification is for interactions with the OS. Its not going to catch driver specific exceptions.

Animats 2y ago
If the driver can dereference nil, it shouldn't pass the Static Driver Verifier.[1] [1] https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/nullcheck https://learn.microsoft.com/en-us/windows-hardware/drivers/d...
- whyever 2y ago
  Not all potential null dereferences are covered by the verifier, they even give an example where the rule is not triggered, but null may be dereferenced by the code.
  - Animats 2y ago
    Now that's a bug. If it can't be ruled out at compile time, there should have to be a check at run time.