diff options
| author | Corey Hickey <bugfood-c@fatooh.org> | 2018-01-13 04:16:37 -0800 |
|---|---|---|
| committer | Stéphane Lesimple <speed47_github@speed47.net> | 2018-01-13 13:16:37 +0100 |
| commit | 4a2d0512850e8da12a2110b33da17c7ec3c7838c (patch) | |
| tree | b04c101ff30b212e2511e265830bf7c6d37995e1 /README.md | |
| parent | f3551b9734850463ccc6d9761e5db0df9cb54fab (diff) | |
| download | spectre-meltdown-checker-4a2d0512850e8da12a2110b33da17c7ec3c7838c.tar.lz spectre-meltdown-checker-4a2d0512850e8da12a2110b33da17c7ec3c7838c.tar.xz spectre-meltdown-checker-4a2d0512850e8da12a2110b33da17c7ec3c7838c.zip | |
minor is_cpu_vulnerable() changes (#71)
* correct is_cpu_vulnerable() comment
As far as I can tell, the function and usage are correct for the comment
to be inverted.
Add a clarifying note as to why the value choice makes sense.
* exit on invalid varient
If this happens, it's a bug in the script. None of the calling code
checks for status 255, so don't let a scripting bug cause a false
negative.
* no need to set vulnerable CPUs
According to comment above this code:
'by default, everything is vulnerable, we work in a "whitelist" logic here.'
Diffstat (limited to 'README.md')
0 files changed, 0 insertions, 0 deletions